- Docs
- Observability
- Alerting
Alerting
- Set up Alertmanager Deploy Alertmanager as its own object, hold its config in a Secret, load rules with PrometheusRule objects, and confirm an alert flows end to end.
- Alert routing and receivers Route alerts by severity, team, and cluster to Slack, PagerDuty, email, or a webhook, so the right person is paged and clients are separated.
- Platform alert rules Some conditions never trigger self-healing on bare-metal pools, so alerting is the only way to act on node integrity and capacity, and this page ships those rules.
- SLOs and error budgets Define service-level objectives on your own metrics and alert on burn rate instead of raw thresholds, so pages mean a real customer problem.
- Silences and grouping Group related alerts into one notification and silence known noise during maintenance, so on-call is not buried when a node pool rolls.