{% from "_monitoring_widgets.html" import context_help with context %} {% set state_badges = {"ok": "status-success", "warning": "status-warning", "high": "status-warning", "critical": "status-danger", "down": "status-danger", "error": "status-danger", "affected": "status-warning", "unknown": "status-warning", "no_checks": "status-neutral"} %}

Monitoring coverage

A compact inventory-level view of enabled monitoring paths. Use Operations for full live detail.

Open Operations

Assets covered

{{ monitoring_coverage.covered_asset_count }}

Assets with at least one enabled check

Enabled checks

{{ monitoring_coverage.enabled_check_count }}

Across active inventory assets

Overall health

{{ monitoring_coverage.overall_state }}

Worst current enabled-check state

Alerts requiring attention

{{ monitoring_coverage.current_alert_count }}

Current unacknowledged alerts

{% if monitoring_coverage.topology_roots %}
{% for root in monitoring_coverage.topology_roots %}{{ root.name }}{{ root.check_count }} enabled checks ยท {{ root.alert_count }} alerts{{ 'No checks' if root.state == 'no_checks' else root.state }}{% endfor %}
{% endif %} {% call context_help("What monitoring coverage means") %}

Coverage means an active inventory asset has at least one enabled registry-backed check. Health and alert values come from the same server-authoritative Operations snapshot; this summary does not invent values for missing telemetry.

{% endcall %}