Field guide
See what Watchdog notices.
Explore a successful run, an overdue job and a repeated tool cycle in a read-only sample workspace. No signup required.
Code and examples reviewed
Read-only sample workspaceSynthetic examples · No account data · No alerts sent
Daily research report
A legitimate 15-minute run. Lifecycle-only setup stays quiet until its 20-minute deadline.
- Run status
- success
- Runtime
- 900 seconds
- Incidents
- 0
No incident. Progress monitoring is off, so a healthy 15-minute run does not trigger a five-minute silence alarm.
Monitoring coverage
- Lifecycle monitoring
- ActiveStart, completion and reported failures. A silent process crash is not directly observed.
- Runtime deadline
- Active1200 seconds from the received run start.
- Progress monitoring
- Not configuredOff. Add meaningful progress signals, then explicitly enable a milestone timeout.
- Tool-loop detection
- Not connectedRequires received tool events with argument fingerprints. Repeated legitimate work needs progress signals.
- Outcome verification
- Not configuredA normal exit alone does not verify the business result.
Connection status reflects the latest recorded run, not a continuous connection. Verify a fresh run after changing instrumentation.
Received sample events (2)
run.startedrun.completed
These fixed examples use Watchdog’s detector logic. They demonstrate interpretation, not a live connection or successful alert delivery. Reproduce the Failure Lab.