[Solved] Given this Alertmanager config snippet: receivers: - name: 'ops-team' email_configs: - to: 'ops@example.com' routes: - receiver: 'ops-team' match: severity:... | Kubernetes

Kubernetes - Monitoring and Logging

Given this Alertmanager config snippet:

receivers:
- name: 'ops-team'
  email_configs:
  - to: 'ops@example.com'
routes:
- receiver: 'ops-team'
  match:
    severity: critical

Why are alerts with severity=warning not delivered to any receiver?

ABecause the receiver name 'ops-team' is invalid.

BBecause email_configs is misconfigured and blocks warnings.

CBecause Alertmanager does not support severity=warning by default.

DBecause the route only matches alerts with severity=critical, so warnings are unmatched.

Step-by-Step Solution

Solution:

Step 1: Analyze route matching
The route matches only alerts with label severity: critical.
Step 2: Consider unmatched alerts
Alerts with severity=warning do not match this route and have no fallback route defined.
Final Answer:
Because the route only matches alerts with severity=critical, so warnings are unmatched. -> Option D
Quick Check:
Routes filter alerts by labels; unmatched alerts have no receiver [OK]

Quick Trick: Routes match labels strictly; unmatched alerts are dropped [OK]

Common Mistakes:

Master "Monitoring and Logging" in Kubernetes

9 interactive learning modes - each teaches the same concept differently

More Kubernetes Quizzes

Given this Alertmanager config snippet: