Home / Templates / Monitor Inventory and Alert Routing Worksheet
Free worksheet

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.

Download the worksheet (.csv)

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.

TargetCheck typeIntervalFailure definitionAlert routeOwner and runbookPublic?
Marketing homepageHTTPS with content match3 minNon-200 or footer text missingChat channel onlyYour name / runbook linkYes
App login pageHTTPS with content match1 minNon-200 or login form missingChat, then call after 5 minYour on-call / runbook linkYes
Public API health endpointHTTPS with JSON field check1 minStatus field not ok, or database field falseChat, then call after 5 minYour on-call / runbook linkYes
Checkout flowSynthetic transaction5 minAny step fails or exceeds your latency limitChat, then call after 10 minYour name / runbook linkYes
Webhook receiverHTTPS POST with test payload2 minNon-2xx on the test payloadChat, then call after 10 minYour name / runbook linkYes
Queue workerHeartbeatPing expected every 5 minNo ping for 15 minChat, then call after 15 minYour on-call / runbook linkNo
Nightly report jobHeartbeatPing expected daily by 06:00No ping within 60 min of the windowChat plus daily digestYour name / runbook linkNo
Certificate for main domainSSL expiryDailyFewer than 14 days remainingChat plus emailYour name / runbook linkNo
DNS for API subdomainDNS resolution5 minRecord missing or wrong valueChat, then call after 10 minYour on-call / runbook linkNo
Mail serverTCP port check5 minConnection refused or timeoutChat channel onlyYour name / runbook linkNo
Your next targetYour check typeYour intervalYour failure ruleYour alert routeYour owner / runbook linkYour call

Also from PingCrumb