---
title: "Incident, response, and learning | Grafana Labs"
description: "Incident declaration, severity tracking, role assignment, timeline, task management, and post-incident reviews."
---

> For a curated documentation index, see [llms.txt](/llms.txt). For the complete documentation index, see [llms-full.txt](/llms-full.txt).

## Grafana Incident

With [Grafana Incident](/docs/grafana-cloud/alerting-and-irm/irm/manage-incidents/) in Grafana Cloud, you can:

- Declare and manage incidents with severity levels and status tracking.
- Assign roles so everyone knows what they’re responsible for.
- Track a timeline of all events and actions during the incident.
- Manage tasks during the response.
- Auto-generate post-incident reviews from the timeline.
- Surface patterns across incidents so recurring failures get addressed.

You keep the alerting tools you already have. IRM sits inside the same platform where your metrics, logs, and traces already live. Grafana IRM bundles Grafana Incident and Grafana OnCall. You don’t have to use both. Each is enabled separately in Grafana Cloud.

## What keeps you up at night?

Role / WorriesWhat you get with the app

**On-Call Engineer, SRE**

- I get paged, open PagerDuty to manage the incident, then switch to Grafana to investigate
- Every minute jumping between tools is a minute the incident isn’t resolved

<!--THE END-->

- On-call management and investigation live in the same platform as your metrics, logs, and traces. No tab-switching during an active outage.
- Grafana Assistant Investigations correlates alerts with observability data automatically, so you spend less time manually piecing together what happened

**Developer pulled into an incident**

- Not on-call, but dragged into incidents anyway
- Don’t know the incident tool, don’t know where to look, and by the time I’m up to speed the incident is already half over

<!--THE END-->

- Incident context (timeline, affected services, linked alerts) is surfaced alongside the observability data you already know
- Automated task assignment means you know exactly what you’re responsible for without needing to know how the incident tool works

**Engineering Manager running post-incident reviews**

- Keep having the same incidents
- Post-mortems are manual, take days, and half the time don’t get done at all

<!--THE END-->

- Post-incident reviews are auto-generated from the incident timeline, not assembled manually
- Patterns across incidents are surfaced so recurring failures don’t get missed

**VP Engineering, Finance**

- Paying for PagerDuty seats for every engineer whether they respond to incidents or not
- Most of those seats are idle most of the time

<!--THE END-->

- Active user pricing: you pay for engineers who actually respond to incidents, not provisioned seats sitting unused
- Teams typically save 40 to 60% compared to per-seat tools like PagerDuty, and IRM is included in the same Grafana Cloud bill you already have