
Capabilities | ||
|---|---|---|
Resolve where your signals live | Keep on-call, routing, and incidents inside Grafana Cloud IRM so a page opens beside your dashboards, logs, and traces. Send an incident or alert to Grafana Assistant for AI-powered investigation, then post the findings back to the incident timeline. Learn more | Chase context across tools after the page lands. An incident opens in a separate console, then troubleshooting usually means pivoting back to your monitoring, logs, and traces to rebuild the story across tabs and handoffs |
Open by default (OTel & Prometheus) | Deploy your Grafana Alloy collector (100% OTLP, Prometheus pipelines), ingest signals once, then route them into alerting, on-call, and incident workflows so response starts with context. Learn more | Trigger incidents from your OpenTelemetry-based monitoring, but rely on those tools to collect metrics, logs, and traces—PagerDuty isn’t the telemetry store. |
Predictable IRM cost | Bill by monthly active IRM users (people on your schedules/escalations or taking IRM actions) so cost tracks to who actually responds. Learn more | License your responders by seat and bolt on extras (e.g., Runbook Automation, AIOps) so spend follows headcount and add-ons as teams scale. |
Page to fix in one view | Open your alert beside dashboards/logs/traces in an incident workspace and cut noise with grouped notifications for the first responder. Learn more | Mobilize your responders and run automations, then pivot to external dashboards/tools for investigation through integrations. |
Works with your stack | Pull in signals from the monitoring you already run, then sync incident work into Slack, Jira, ServiceNow, and GitHub so the tools your teams live in stay aligned. ServiceNow sync is bidirectional, and GitHub issues stay in sync with incident details, while the incident timeline stays in Grafana. Learn more | Route events from 700+ tools into paging, then coordinate tickets and comms across separate systems as the incident evolves. That split workflow creates handoffs where context and status can drift. |
Guided investigations with AI | Utilize the Knowledge Graph for contextual, automated root-cause analysis and Grafana Assistant Investigations to correlate metrics, logs, traces, and profiles within your workspace. Learn more -> | Purchase PagerDuty AIOps to reduce noise and orchestrate events across your services. |
Switch fast, keep control | Define your on-call schedules, escalations, routes, and integrations as code with the Grafana Terraform provider, then follow the PagerDuty-specific migration path to cut over service-by-service without breaking paging. Keep changes reviewable in git, and keep coverage intact while you switch. Learn more -> | Operate today with APIs/Terraform, but expect manual mapping when moving configurations to a new target. |








