Source
Documentation (on-call schedules) — Grafana IRM
Checked for Grafana IRM on 6 Nov 2026
- Page
- https://grafana.com/docs/grafana-cloud/observe-and-act/respond-to-incidents/on-call-schedules/
- Checked
- 6 Nov 2026, 04:30 UTC
- How we may use it
- Public page, crawling permitted
Technical details
- type
- page
- http status
- 200
- content hash
- sha256:b5948e6e7471ff0ab44a93e8a637cab6ef6f249a112758b65e057f37994de534
- permission
- robots_ok
- screenshot
- Screenshot on file (internal exhibit, not published)
Cited by
Facts read from this source
-
Oncall schedules purpose Report an error
“Use on-call schedules in Grafana IRM to establish automatic rotation management and alert escalation.”
-
Schedule concepts Report an error
“Rotations: Recurring patterns that determine when team members are on-call, such as weekly or monthly cycles Shifts: Specific time periods when a team member is responsible for responding to incidents and alerts Schedule layers: Multiple concurrent rotation patterns that define different response priorities (a higher-level layer overrides a lower tier rotation) Time zones: Settings that ensure accurate schedule display and management for distributed teams across regions Overrides: Temporary schedule modifications to accommodate time off, shift swaps, or special coverage needs”
-
Schedule types Report an error
“Grafana IRM offers three flexible ways to manage on-call schedules: IRM app managed schedules Create and manage schedules directly through the Grafana IRM web UI”
-
Irm app schedule capabilities Report an error
“Design custom rotation patterns that match your team’s needs Configure multiple rotation layers Preview and validate schedule coverage in real-time Handle overrides and time zone adjustments”
-
Ical import Report an error
“Import schedules from calendar applications like Google Calendar: Manage rotations using familiar calendar tools Import schedules via iCal URLs Automatically sync schedule changes Set up override calendars for temporary coverage adjustments Support priority levels for overlapping shifts”
-
Schedules as code Report an error
“Manage schedules programmatically through Terraform and version control: Define schedules as code Track schedule changes in version control Automate schedule creation and updates Integrate with CI/CD pipelines Ensure consistent schedule configuration Scale schedule management across teams”
-
Schedule quality metrics Report an error
“Monitor and improve your schedule effectiveness: Quality metrics Coverage gaps Distribution balance User workload Schedule predictability”
-
Quality score scale Report an error
“The schedule quality score (0-100) helps you assess and improve your schedules”
-
Quality score ratings Report an error
“81-100 Great Well-balanced, consistent coverage 61-80 Good Minor improvements possible 41-60 Medium Some gaps or imbalances 21-40 Low Significant improvements needed 0-20 Poor Major coverage issues”
-
Quality score deleted users impact Report an error
“If the schedule includes users which were deleted or users without the required permissions to be on-call, that will also affect the quality score.”
-
Escalation chains with schedules Report an error
“By defining an escalation chain including several “Notify schedule” steps with a “Wait” step between them, you can organize different levels of on-call responsibility:”
-
Escalation levels Report an error
“Primary level First line of defense for incident response Handles initial incident assessment and resolution Typically staffed by team members most familiar with the system Secondary level Provides backup support when primary cannot respond Activated if primary doesn’t acknowledge within set timeframe Often includes more experienced team members or specialists Tertiary level Final escalation point for critical incidents Ensures coverage when primary and secondary are unavailable May include senior team members or management”
-
Layered schedule benefits Report an error
“Distributes on-call workload across teams Provides clear escalation paths Ensures continuous coverage for critical systems Allows for specialized response teams”
-
Schedule examples documented Report an error
“Schedule examples Shift swaps and overrides Notify responders”
Scores citing this record
- The Engineering Manager On-call schedules, rotations & escalation
- The Engineering Manager Integrations, API & administration
- The ICT Risk Officer On-call schedules, rotations & escalation
- The ICT Risk Officer Integrations, API & administration
- The IT Operations Manager On-call schedules, rotations & escalation
- The IT Operations Manager Integrations, API & administration
- The MSP NOC Lead On-call schedules, rotations & escalation
- The MSP NOC Lead Integrations, API & administration
- The Skeptic On-call schedules, rotations & escalation
- The Skeptic Integrations, API & administration
- The SRE Lead On-call schedules, rotations & escalation
- The SRE Lead Integrations, API & administration