Monitor Inventory and Alert Routing Worksheet
One sheet that records every check you run, what counts as failure, how often it runs, where alerts go, and who owns the response.
Reviewed for 2026, updated September 8, 2026.
A monitoring setup decays quietly. Endpoints get renamed, a check keeps pointing at an old URL, someone leaves and their number stays in the escalation policy. The fix is a single inventory that lists every monitor in one place with its interval, its definition of failure, its alert route, and a named owner. Reviewing that sheet once a month takes less time than one confusing incident, and it makes on-call possible for a small team because the next person can see exactly what each check does and what to do when it fires.
The rows below are examples, not recommendations for your product. Replace the targets with your own endpoints and jobs, and fill in the placeholders. The Public column marks which checks feed the availability number on your status page, a distinction explained in our guide at /guide/. For the interval column, our calculator at /tools/check-interval-detection-time/ turns interval and confirmation settings into an expected detection time, and our checklist for monitoring APIs and webhooks at /blog/monitoring-apis-webhooks-checklist/ covers heartbeat rules for background jobs.
| Target | Check type | Interval | Failure definition | Alert route | Owner and runbook | Public? |
|---|---|---|---|---|---|---|
| Marketing homepage | HTTPS with content match | 3 min | Non-200 or footer text missing | Chat channel only | Your name / runbook link | Yes |
| App login page | HTTPS with content match | 1 min | Non-200 or login form missing | Chat, then call after 5 min | Your on-call / runbook link | Yes |
| Public API health endpoint | HTTPS with JSON field check | 1 min | Status field not ok, or database field false | Chat, then call after 5 min | Your on-call / runbook link | Yes |
| Checkout flow | Synthetic transaction | 5 min | Any step fails or exceeds your latency limit | Chat, then call after 10 min | Your name / runbook link | Yes |
| Webhook receiver | HTTPS POST with test payload | 2 min | Non-2xx on the test payload | Chat, then call after 10 min | Your name / runbook link | Yes |
| Queue worker | Heartbeat | Ping expected every 5 min | No ping for 15 min | Chat, then call after 15 min | Your on-call / runbook link | No |
| Nightly report job | Heartbeat | Ping expected daily by 06:00 | No ping within 60 min of the window | Chat plus daily digest | Your name / runbook link | No |
| Certificate for main domain | SSL expiry | Daily | Fewer than 14 days remaining | Chat plus email | Your name / runbook link | No |
| DNS for API subdomain | DNS resolution | 5 min | Record missing or wrong value | Chat, then call after 10 min | Your on-call / runbook link | No |
| Mail server | TCP port check | 5 min | Connection refused or timeout | Chat channel only | Your name / runbook link | No |
| Your next target | Your check type | Your interval | Your failure rule | Your alert route | Your owner / runbook link | Your call |
https://pingcrumb.com/templates/monitor-inventory-worksheet/Use it in your business, share it with your team, or link to it from your own site.
Also from PingCrumb
- Uptime Monitoring Setup Checklist: A step-by-step checklist for setting up checks, alerting, and a status page that a small software team can actually maintain.
- Free calculators