Grafana IRM
Let AI connect your sources for you
Skip the manual setup — run this in your project and the wizard auto-detects your databases and APIs and connects them to PostHog.
Connect Grafana IRM to PostHog to sync your data into the PostHog data warehouse for analysis and modeling.
Sync your Grafana IRM alert groups, incidents, schedules and escalation setup into the PostHog Data warehouse.
Create a service account token under Administration > Users and access > Service accounts in your Grafana Cloud stack. Give the service account the Viewer role, or the IRM reader permissions for the tables you want to sync.
Find the OnCall API URL in Grafana under IRM > Settings > Admin & API.
Configuration
| Option | Type | Required |
|---|---|---|
Grafana stack URL | text | Yes |
OnCall API URL | text | Yes |
Service account token | password | Yes |
Linking Grafana IRM to PostHog
- Go to the Data pipeline page in PostHog
- Click New source and select Grafana IRM
- Fill in the required configuration fields
- Click Next, select the tables you want to sync, and then press Import
Supported tables
| Table | Description | Sync method | Incremental field | Primary key |
|---|---|---|---|---|
alert_groups | OnCall alert groups. Full refresh only: the API lists newest first and states change after creation | Full refresh | — | — |
resolution_notes | A note attached to an alert group that explains how it was resolved. | Full refresh | — | — |
integrations | A monitoring integration that sends alerts into OnCall, with its default route and message templates. | Full refresh | — | — |
routes | A rule that sends matching alerts from an integration to an escalation chain. | Full refresh | — | — |
escalation_chains | A named sequence of escalation policies that decides who is notified and when. | Full refresh | — | — |
escalation_policies | A single step of an escalation chain, such as waiting or notifying users or schedules. | Full refresh | — | — |
schedules | An on-call schedule that defines who is on call at any time. | Full refresh | — | — |
on_call_shifts | A shift or rotation that belongs to one or more on-call schedules. | Full refresh | — | — |
shift_swaps | A request from one user to hand over their on-call shifts for a period to another user. | Full refresh | — | — |
users | A Grafana user known to OnCall. | Full refresh | — | — |
teams | A Grafana team as seen by OnCall. | Full refresh | — | — |
user_groups | A Slack user group that OnCall can notify. | Full refresh | — | — |
incidents | A Grafana incident: a declared problem with its severity, status, timeline bounds and people involved. | Full refresh | — | — |
incident_activity | Timeline entries of every incident. Fetched per incident, so large incident histories take longer | Full refresh | — | — |