Skip to main content
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 reviews the target, monitor type, interval and destination before creating it. Plans apply to significant cloud work, not every monitor action.
During an incident, start here to see everything that’s firing, then drop into Grafana traces or the agent to chase the root cause.

​
Check freshness and delivery

Provider reads can fail independently; review any provider error before treating a partial overview as complete health. A new monitor can take a refresh cycle to appear. Its presence proves configuration exists, not that incident notifications reach someone. Verify the provider’s outgoing webhook and destination separately. For resources with no public endpoint, use the cluster’s metrics and alerting pipeline instead of inventing an external HTTP probe for each Deployment or Node. Ask the agent to inspect existing datasources and monitoring before adding probes.