monitoring
2 articles about "monitoring".
Exit code 0 is not success: how we check 50+ Windows scheduled tasks for real
Task Scheduler showed 0x0 while our Telegram watchdog actually exited 255 and never restarted anything. We stopped trusting result codes: every task writes its own start and end markers, a checker reads them, and no success within the time limit means red. 52 tasks covered, 1 left. Includes a VBS wrapper, the cmd errorlevel trap and a Node checker skeleton.
The Dashboard Said Running. The Service Had Done Nothing All Night: Four Silent Failures in Automation Monitoring
A running flag that was always false, a heartbeat that measured presence instead of work, alert dedup that muted a real outage, and an auto-stop with no auto-resume. Four real bugs from our automation fleet, each with the broken check, why it lied, and the check that replaced it.