skills.rest
1k-off
1k-offCOMMUNITY
Explore all skills by this author →
WebsiteGitHub

alerting-irm

Provision Grafana alert rules, contact points, and notification policies via YAML.

1|Updated May 21, 2026
Search Tags:#grafana#alerting#on-call#slo#burn-rate#irm#notification routing
One-click install
npx skills add https://github.com/1k-off/umbraco-observability-playground --skill alerting-irm-1k-off
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: alerting-irm
Source: https://github.com/1k-off/umbraco-observability-playground/tree/main/.agents/skills/alerting-irm
Command: npx skills add https://github.com/1k-off/umbraco-observability-playground --skill alerting-irm-1k-off

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill helps you prevent alert noise and missed responses by providing a practical blueprint for Grafana Alerting and Incident Response Management (IRM), including SLO burn-rate alerts and end-to-end notification routing.

Core Features & Use Cases

  • Grafana-managed alerting provisioning: Define alert groups, rules, expressions, and lifecycle states (including NoData/Error handling) in YAML so alerting can be deployed and reviewed like code.
  • Data source-managed rule examples: Cover Prometheus/Mimir ruler-style alert rules (including recording rules) and Loki LogQL-based alerting for log-driven incidents.
  • Notification routing for on-call: Set up contact points (Slack/PagerDuty/email/webhook), build notification policies, and use silences/mutes to control who gets paged and when.
  • SLO configuration with burn-rate alerts: Generate SLO-related recording rules and burn-rate alerting logic for availability and error budgets.
  • IRM on-call workflows: Outline on-call schedules, escalation chains, incident collaboration, and integration sources to connect alerts to operational response.

Quick Start

Provision Grafana alert rules, contact points, and notification policies by generating the YAML templates for alerting/routing, then apply them via Grafana provisioning APIs so incidents and SLO burn-rate alerts route to the correct on-call channels.

Frequently Asked Questions about alerting-irm

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

FAQPage Schema
How do I set up Grafana alerting notification routing for on-call schedules?▼

Grafana alerting notification routing is configured by defining contact points and notification policies in YAML. You can route alerts to specific on-call channels like Slack, PagerDuty, or email using silences and muting to control who gets paged.

What is an SLO burn-rate alert and how does it work in Grafana?▼

An SLO burn-rate alert in Grafana triggers when your error budget is consumed too quickly. It works by generating recording rules and alerting expressions that measure availability against your configured service level objectives, detecting potential violations early.

Can I provision Prometheus ruler and Loki LogQL alert rules together in Grafana?▼

Yes, you can provision Prometheus ruler-style alert rules and Loki LogQL log alerts together in Grafana. This Skill supports defining both data source-managed recording rules and log-driven alerting in YAML for reliability, latency, and error-rate scenarios.

How do I write YAML definitions for Grafana alert rules and contact points?▼

You write YAML definitions for Grafana alert rules and contact points by specifying alert groups, rule expressions, lifecycle states, and NoData handling. These YAML templates are then applied via Grafana provisioning APIs to deploy alerts as code.

Does Grafana alerting support muting and silences for incident response management?▼

Yes, Grafana alerting supports muting and silences for incident response management. You can configure notification policies with silences to suppress alerts during maintenance windows or active incidents, preventing alert noise and unnecessary pages.

What's the best way to manage incidents and escalation chains with Grafana alerting?▼

The best way to manage incidents with Grafana alerting is to define escalation chains and on-call schedules in your notification policies. This connects alerts to operational response through integration sources, ensuring incidents route to the correct responders.

Related Skills

Explore More Software Engineering Skills→
Prompt-or-Die-LabsPrompt-or-Die-Labs
7

sla-monitor-generator

Generate Prometheus/Alertmanager SLO monitoring configurations from reliability targets.

Official
Intermediate
chicongstchicongst
2

sre-engineering

Coordinate production incident response and post-mortem analysis.

Community
Advanced
infiquetrainfiquetra
8

pagerduty-teams

Manage PagerDuty teams, escalation policies, and on-call schedules via Python client.

Official
Advanced
curiositechcuriositech
2

monitoring-stack-deployer

Deploy Prometheus, Grafana, and SLO-driven alerting on Kubernetes clusters.

Official
Advanced