The Monitoring view brings together the health signals from your connected
observability tools — Grafana and
Better Stack — into a single, unified picture. Rather
than tab-hopping between consoles, you see monitors, heartbeats, alert rules, and
incidents in one place.
What aggregates here
- Monitors & heartbeats — uptime and liveness checks.
- Alert rules — what’s configured to fire, and what’s firing now.
- Incidents — active and recent.
Reads are aggregated across Grafana,
Better Stack and GCP — every row
links through to its source provider for the full detail.
Other providers are browsable, but on their own pages rather than here: AWS has
CloudWatch alarms, metrics, and log groups under its account, and Uptime Kuma has
its monitors. Only the three above feed this unified view.
Acting from the overview
Rows are not inert. Each one offers:
- Watch with Agent — hand the monitor or alert rule to the agent as a
Watch, and pick where it should report when the rule fires.
- Open in provider — jump to the rule in its own console.
- Delete — remove the underlying rule, where the provider supports it.
Creating a monitor from scratch still happens either in the provider’s own
console or by asking the agent, which proposes a
plan when a change is involved.
During an incident, start here to see everything that’s firing, then drop into
Grafana traces or the agent to chase the root cause.
