Incident log
Every outage the prober has caught. When a service stops responding, the pipeline files a GitHub issue automatically and closes it on recovery — the same alert → resolve loop used in production on-call.
No incidents in the recorded history.
10 checks ran across 5 services — last check 22d ago. An empty log with a running prober is the good outcome. If anything I monitor goes down, the pipeline files a GitHub issue automatically and it shows up here.