Calculate the percentage of infrastructure and services covered by active monitoring.
Overall coverage = monitored_services / total_services × 100, but treating all services as equally important hides the highest-risk gaps — a service classified as business-critical with no monitoring is a much bigger operational risk than a low-traffic internal tool with no monitoring. This calculator reports both the overall coverage percentage and a separate critical-service coverage figure, and flags any gap in critical coverage as the top-priority finding regardless of overall percentage.
coverage_percent = (monitored_services / total_services) × 100
A single unmonitored critical service can cause a major undetected outage, while many unmonitored low-priority services collectively pose less risk — prioritizing by business impact rather than raw percentage avoids spending effort on low-value instrumentation while critical blind spots persist.
This model treats a service as monitored if it has active metrics scraping, at least a basic dashboard, and some alerting — a service with only logs but no metrics/alerts, or only a dashboard nobody's alerting on, arguably shouldn't count as fully covered.
Cross-reference your service catalog/CMDB or Kubernetes namespace list against your Prometheus service-discovery targets or Grafana dashboard list — services present in the former but absent from the latter are your gap list.
No — coverage measures breadth (is there *any* monitoring) not depth or quality (are the right SLIs tracked, are alerts well-tuned). Pair this metric with alert noise score and SLI/SLO tracking for a fuller picture of monitoring maturity.