Practice vocabulary for alerting strategy: SLI/SLO-based alerting, evaluation windows, alert severity, maintenance suppression, and alert fatigue.
0 / 5 completed
1 / 5
An alert that activates when a measured service level indicator drops below the service level objective target is described as:
The alert fires when the SLI breaches the SLO threshold — SLO-based alerting is preferred over arbitrary threshold alerts because it directly ties alerts to user experience.
2 / 5
The time period over which a Prometheus/Grafana alert rule continuously evaluates before firing is called:
The alert has a 5-minute evaluation window — the 'for' clause in Prometheus alerting rules prevents flapping by requiring the condition to persist for the full window.
3 / 5
When an alert is classified as requiring acknowledgment from the on-call engineer within 30 minutes, its severity is described as:
The alert severity is P2 — acknowledge within 30 minutes — P1 requires immediate response, P2 within 30 minutes, P3 within business hours; severity sets on-call expectations.
4 / 5
When alerts are automatically paused during a scheduled maintenance window to prevent unnecessary notifications, this is called:
The alert is suppressed during maintenance windows — tools like PagerDuty, OpsGenie, and Alertmanager support scheduled silences or inhibition rules for planned maintenance.
5 / 5
When an on-call team receives so many alerts that they begin ignoring them or become desensitized to their urgency, this is called:
Alert fatigue vocabulary — when every alert feels meaningless, real incidents get missed. Solutions include reducing noisy alerts, improving grouping, and moving to SLO-based alerting.