monitoring-alerting

Solid

Monitoring and alerting design reviewer for production backend services. ALWAYS use when writing Prometheus alerting rules, designing Grafana dashboards, defining SLI/SLO, configuring alert routing (PagerDuty/OpsGenie/Slack), or reviewing existing monitoring setups. Covers SLI/SLO definition, alert rule quality (sensitivity/specificity tradeoff), burn-rate alerting, alert fatigue prevention, dashboard design principles, label cardinality management, and on-call routing configuration. Use even for "just add an alert" — a poorly designed alert either pages at 3AM for non-issues (alert fatigue) or stays silent during real outages (false confidence).

AI & Automation 30 stars 5 forks Updated today MIT

Install

View on GitHub

Quality Score: 85/100

Stars 20%
50
Recency 20%
100
Frontmatter 20%
70
Documentation 15%
100
Issue Health 10%
80
License 10%
100
Description 5%
100

Skill Content

# Monitoring & Alerting Design Review ## Quick Reference | If you need to… | Go to | |----------------------------------------|------------------------------------------| | Scope / prerequisites / depth | §1, §2 Gates, §3 Depth | | Handle incomplete context | §4 Degradation Modes | | Evaluate the design item by item | §5 Design Checklist | | Validate rules before shipping | §5.5 Rule Validation | | Avoid common alerting mistakes | §6 Anti-Examples | | Score, then format the output | §7 Scorecard, §8 Output Contract | | SLI/SLO, burn-rate, error budget | `references/sli-slo-patterns.md` | | Alert anti-patterns and fatigue | `references/alert-anti-patterns.md` | | Routing / grouping / inhibition config | `references/alertmanager-config-patterns.md` | --- ## §1 Scope **In scope** — monitoring and alerting for production backend services: - SLI (Service Level Indicator) definition and measurement - SLO (Service Level Objective) target setting and error budget - Prometheus alerting rules (PromQL, `for` duration, severity labels) - Burn-rate alerting (multi-window, multi-burn-rate SLO alerts) - Grafana dashboard design (layout, variable templating, panel types) - Alert routing configuration (PagerDuty/OpsGenie/Slack, severity-based ...

Details

Author
johnqtcg
Repository
johnqtcg/awesome-skills
Created
6 months ago
Last Updated
today
Language
Python
License
MIT

Integrates with

Anthropic · AI Grafana · Monitoring

Similar Skills

Semantically similar based on skill content — not just same category

Web & Frontend Listed

observability-designer

Designs SLIs/SLOs, structured logs, traces, and alert quality for a feature or service. Use when shipping new paths or fixing noisy/missing alerts. Emits OBS_PLAN. Never recommends alert spam or metrics without a user/journey signal.

0 Updated 1 months ago
willianbs
AI & Automation Listed

observability-designer

SLO/SLI design, alert optimization, and dashboard generation for production services. TRIGGER when: user asks to define SLOs, design alerts, create dashboards, reduce alert fatigue, set error budgets, or improve observability; user runs /observability or /slo. DO NOT TRIGGER when: debugging a specific incident (use debugging tools), writing application code, configuring CI/CD pipelines.

1 Updated 1 weeks ago
DROOdotFOO
DevOps & Infrastructure Listed

monitoring-alerting

Set up monitoring and alerting for production systems — logs, metrics, traces, SLIs/SLOs, alert rules, and dashboards. Use when setting up observability, configuring alerts, defining SLOs, building a dashboard, or debugging why an alert didn't fire. This skill is specific to observability and alerting configuration and does NOT cover CI/CD pipelines, containerization, or secret management.

1 Updated 1 months ago
ecoma-io