infra-alert-fatigue-reduction

Implement SLO-based multi-window burn-rate alerting in Prometheus and AlertManager.

14|1|Updated May 5, 2026
One-click install
npx skills add https://github.com/ivanshamaev/de-agent-skills --skill infra-alert-fatigue-reduction
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: infra-alert-fatigue-reduction
Source: https://github.com/ivanshamaev/de-agent-skills/tree/main/group_skills/infra_dataops_group_skills/infra_alert_fatigue_reduction
Command: npx skills add https://github.com/ivanshamaev/de-agent-skills --skill infra-alert-fatigue-reduction

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill reduces alert fatigue by replacing noisy threshold alerts with SLO-based multi-window burn-rate alerting, and by improving AlertManager routing, inhibition, and deduplication so on-call teams get fewer, more actionable pages.

Core Features & Use Cases

  • SLO-based burn rate alerting: Implements critical and warning alerts using short/long evaluation windows to detect both fast and sustained error budget burn.
  • Alert quality standards: Enforces required labels (e.g., severity, ownership, paging intent) and runbook-linked annotations to keep alerts actionable.
  • Noise reduction with AlertManager: Adds routing by severity (PagerDuty for critical, Slack for warning), groups/deduplicates alerts, and uses inhibition rules to suppress derived child alerts when parent alerts fire.
  • Flapping and duration tuning: Uses appropriate for durations and timing guidance to avoid transient spikes triggering pages.
  • Weekly alert noise audit & review process: Supports a repeatable workflow to identify top-firing noisy alerts and decide whether to fix, demote, rewrite, or delete them.
  • Alert ownership model and escalation: Encourages team labels and ticket-based escalation for warning-level noise to keep warning storms from becoming page storms.

Quick Start

Use the infra-alert-fatigue-reduction Skill to generate SLO burn-rate Prometheus alert rules plus an AlertManager configuration that routes critical pages to PagerDuty, warnings to Slack, and suppresses redundant/derived alerts with inhibition rules.

Frequently Asked Questions about infra-alert-fatigue-reduction

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I reduce alert fatigue in Prometheus and Alertmanager?

Reduce alert fatigue in Prometheus and Alertmanager by implementing SLO-based multi-window burn-rate alerting, configuring severity-based routing, and applying inhibition rules to suppress redundant pages.

What is SLO-based multi-window burn-rate alerting?

SLO-based multi-window burn-rate alerting uses short and long Prometheus evaluation windows to detect fast and sustained error budget burn, replacing noisy threshold alerts with actionable pages.

How do I stop PagerDuty alert storms from warning-level alerts?

Stop PagerDuty alert storms by routing warning alerts to Slack, routing critical alerts to PagerDuty, and using ticket-based escalation to prevent warning storms from becoming page storms.

How do I configure Alertmanager deduplication and inhibition rules?

Configure Alertmanager deduplication and inhibition by using group_by for grouping and inhibition rules to suppress derived child alerts when parent alerts fire, reducing repetitive noise.

How do I tune Prometheus alert for durations to avoid transient spikes?

Tune Prometheus alert for durations to avoid transient spikes by applying appropriate timing guidance, ensuring transient errors do not trigger immediate pages during data engineering workflows.

How do I audit and review noisy alerts for data engineering on-call workflows?

Audit and review noisy alerts using a weekly process to identify top-firing alerts in data engineering on-call workflows, deciding whether to fix, demote, rewrite, or delete them.