alerting-irm

Automate Grafana alerting, IRM workflows, and SLO management via YAML or API.

Updated Mar 28, 2026
One-click install
npx skills add https://github.com/MisLink/agentry --skill alerting-irm
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: alerting-irm
Source: https://github.com/MisLink/agentry/tree/main/agents/.agents/skills/alerting-irm
Command: npx skills add https://github.com/MisLink/agentry --skill alerting-irm

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Grafana alerting, Incident Response Management (IRM), and SLO configuration can be complex to set up and maintain across rules, contacts, silences, on-call rotations, and burn-rate alerts, leading to delays and misrouting.

Core Features & Use Cases

  • Centralized provisioning of Grafana alert rules (Grafana-managed, Prometheus/Mimir rules, and Loki alerts) and IRM workflows
  • YAML/API provisioning for contact points, notification policies, groups, and SLO configurations to enable repeatable deployments
  • Use Case: Align alert routing, incident management, and on-call schedules across teams to reduce MTTR and improve reliability.

Quick Start

Configure Grafana alerting, IRM, and SLOs in your environment to provision alert rules, contact points, and on-call policies.

Frequently Asked Questions about alerting-irm

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

FAQPage Schema
How do I automate Grafana alerting provisioning for contact points and notification policies?▼

Grafana alerting provisioning is automated by defining alert rules, contact points, and notification policies via YAML or API. This enables repeatable deployments and centralized configuration management across Grafana-managed, Prometheus/Mimir, and Loki alerts.

What is the best way to align Grafana on-call schedules with incident management workflows?▼

Aligning Grafana on-call schedules with incident management involves integrating IRM workflows with on-call rotations and alert routing. This centralized approach reduces alert misrouting and helps improve reliability by streamlining incident response processes.

Can I provision Grafana SLO configurations and burn-rate alerts using YAML?▼

Yes, Grafana SLO configurations and burn-rate alerts can be provisioned using YAML or API. This allows teams to define service level objectives and automated alerting thresholds in a repeatable, version-controlled deployment format.

Does Grafana IRM support centralized alert rule management across multiple data sources?▼

Grafana IRM supports centralized alert rule provisioning across Grafana-managed rules, Prometheus/Mimir rules, and Loki alerts. This consolidates alerting configuration across diverse data sources into a unified management workflow.

Why are my Grafana alert notifications being delayed or misrouted to the wrong teams?▼

Grafana alert notification delays and misrouting often stem from complex, disconnected contact point and policy configurations. Centralizing alert routing, notification policies, and on-call schedules via YAML provisioning ensures alerts reach the correct responders.

How do I set up Grafana incident response management to reduce MTTR?▼

Grafana incident response management reduces MTTR by provisioning integrated alert rules, contact points, and on-call schedules. Aligning these IRM workflows ensures rapid alert delivery and coordinated incident handling across responding teams.