oncall-irm

Route incoming alerts to escalation chains and on-call schedules.

213|18|Updated Mar 17, 2026
One-click install
npx skills add https://github.com/grafana/skills --skill oncall-irm
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: oncall-irm
Source: https://github.com/grafana/skills/tree/main/skills/grafana-cloud/oncall-irm
Command: npx skills add https://github.com/grafana/skills --skill oncall-irm

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Centralizes alert routing and incident lifecycle management so teams can reliably route notifications, escalate issues, and coordinate responders without manual triage overhead.

Core Features & Use Cases

  • Integration endpoints: Configure Alertmanager, Grafana Alerting, formatted webhooks, and custom integrations to receive alerts.
  • Routing templates: Author Jinja2 templates to map incoming alerts to escalation chains and grouping ID templates to consolidate related alerts.
  • Escalation chains & schedules: Define ordered notification steps, waits, team and schedule notifications, iCal or Terraform-backed schedules, and auto-resolve rules.
  • Notifications & integrations: Deliver notifications via Slack, mobile push, SMS, PagerDuty, and outgoing webhooks; support Slack actions for acknowledge/resolve.
  • API & automation: Use REST endpoints to list/create integrations, schedules, escalation chains, and alert groups; support rate limits and Terraform/iCal imports.
  • Use Case: Route production database critical alerts from Prometheus Alertmanager to a primary on-call schedule with escalation to team leads and PagerDuty after defined timeouts.

Quick Start

Configure an Alertmanager webhook integration and create a Jinja2 routing template that sends critical alerts to the Platform escalation chain for testing.

Frequently Asked Questions about oncall-irm

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

FAQPage Schema
How do I route Prometheus Alertmanager alerts to an on-call schedule with escalation?

Consolidate related alerts by defining grouping ID templates using Jinja2 syntax. These templates map incoming alert payloads to a grouping identifier, allowing the incident response system to merge related notifications into a single alert group for streamlined triage.

Can I use Terraform and iCal to import on-call schedules and escalation chains?

Deliver incident notifications via Slack, mobile push, SMS, and PagerDuty. You can also configure outgoing webhooks and enable Slack actions to allow responders to acknowledge or resolve alert groups directly from their chat interface.

Do I need Jinja2 routing templates to configure Alertmanager webhooks?

Yes, Jinja2 routing templates are required to map incoming Alertmanager webhook payloads to the correct escalation chains. They enable dynamic alert routing and grouping ID consolidation based on the content of the incoming alert data.

What are the REST API rate limits when creating alert groups and integrations?

The REST API enforces rate limits when listing and creating integrations, schedules, escalation chains, and alert groups. These limits regulate automated API operations to ensure reliable incident response and routing infrastructure management.