Kubernetes - Monitoring and Logging
You want to avoid alert spam by grouping alerts by both 'alertname' and 'severity', and send notifications to Slack channel '#alerts'. Which Alertmanager route and receiver config is correct?
You want to avoid alert spam by grouping alerts by both 'alertname' and 'severity', and send notifications to Slack channel '#alerts'. Which Alertmanager route and receiver config is correct?
hard📝 Workflow Q15 of 15
Step-by-Step Solution
Solution:
Step 1: Set grouping labels in route
To group alerts by 'alertname' and 'severity', list both in 'group_by'.Step 2: Configure Slack receiver correctly
Receiver named 'slack-notifications' uses 'slack_configs' with channel '#alerts' and 'send_resolved' true.Final Answer:
Route groups by alertname and severity; receiver sends Slack messages to #alerts -> Option CQuick Check:
Group by multiple labels and use correct receiver config [OK]
Quick Trick: Group by multiple labels and match receiver type to notification [OK]
Common Mistakes:
- Using email_configs for Slack notifications
- Grouping by only one label when two needed
- Mismatch between route receiver and receiver name
Master "Monitoring and Logging" in Kubernetes
Want More Practice?
15+ quiz questions · All difficulty levels · Free
Free Signup - Practice All QuestionsMore Kubernetes Quizzes