On-call work is demanding, and exhaustion directly impacts incident response quality, retention, and overall team health. Engineering leaders often lack visibility into when their teams are being stretched too far until it’s too late. Rootly’s On-Call Health changes that by giving you evidence-based insights into engineer well-being.
Connect your incident data, GitHub activity, and Slack communication to detect early signs of burnout. By analyzing response patterns, workload pressure, after-hours activity, and sentiment, On-Call Health highlights teams and individuals at risk—so you can intervene early with data-driven changes to workload distribution and on-call rotations.
This means you can:
- Quantify burnout risk with a validated framework.
- Proactively rebalance rotations before exhaustion impacts reliability.
- Back decisions with concrete data, not just gut feel.
.avif)
How it works
- Connect your tools: Integrates with Rootly and other incident management tools, GitHub, and Slack for the most complete picture.
- Analyze patterns: Looks at incident workload, after-hours activity, escalation frequency, response times, and communication sentiment.
- Adapt to your environment: Works with whatever data sources you have available to give the most accurate assessment possible.
- Generate interventions: Produces Risk-Based Recommendations so you know whether to rotate schedules, adjust workload, or offer recovery time.
Getting started
- Hosted version: Sign up at oncallhealth.ai for a fully managed experience.
- Open source version: Self-host and customize via Rootly-AI-Labs on GitHub.
- MCP Server integration: Connect directly with Rootly’s MCP Server for seamless data ingestion.
This release is about more than efficiency—it’s about safeguarding the people behind your incident response. With early warning signs, Rootly helps you keep your teams healthy, sustainable, and ready for the long run.
New & Improved
New Features
- Alert descriptions are now included in SMS notifications to provide more context for on-call responders
- Team and service slack channels configured via API/Terraform now display their channel names in the UI instead of channel IDs
- Alert field-based routing rules can now be created and managed through the API, Terraform, and UI
- The base email layout has been updated across all system emails for improved consistency and design
- Images embedded in alert notifications now render as visual blocks in Slack instead of clickable URLs
- Status page templates can now be configured to include templated titles for new updates to the status pages
Bug Fixes
- Added pagination support to the shifts API endpoint for better performance when retrieving schedule data
- Resolved a problem where the services search bar wasn't returning newly created services for some customers
- Fixed workflows becoming stale and not executing after being queued for 30 days
- Corrected an issue where certain admin roles couldn't bulk delete alerts from the UI
- Fixed shift update notifications being posted twice for some schedules
- Resolved a bug where escalation policy links were opening the wrong schedule
- Corrected an issue where GitHub and GitLab merge requests attached to Slack incident channels weren't visible on the web
- Fixed a problem where custom incident field changes were displaying raw code in timeline events instead of formatted text
- Resolved an issue where duplicate alert events weren't properly resolving the parent alert when a resolution event was received