Alertmanager is what happens after Prometheus detects a problem — it receives firing alerts and decides where they go, deduplicating and grouping related alerts before routing them to Slack, PagerDuty, email, Microsoft Teams, or a custom webhook.
This category covers configuring that routing layer inside kube-prometheus-stack: defining receivers, writing route-matching rules against alert labels, and using silencing and inhibition to keep on-call engineers from drowning in duplicate notifications.
What the always-firing Watchdog alert is for, how to disable individual default alert rules, and how to point kube-prometheus-stack at an Alertmanager you already run outside the chart.
Read ArticleConfigure Alertmanager in kube-prometheus-stack for Slack, PagerDuty, email and webhook notifications. Complete routing, grouping, silencing, and inhibition guide.
Read ArticleYes — a single route can have multiple child routes, or a receiver configured with multiple integrations (e.g., Slack and PagerDuty together), so one alert reaches several destinations.
Yes — grouping and deduplication are core Alertmanager behaviors, controlled by group_by, group_wait, and group_interval settings in its routing configuration.
