On-Call Health is a free, open-source tool designed for engineering teams to detect on-call burnout detection before it escalates. It falls under the category of on-call health monitoring platforms, specifically targeting engineering managers, infrastructure leads, and incident response stakeholders. Its core value lies in transforming anecdotal feedback into data-backed evidence, enabling teams to make informed decisions about on-call workload and prevent unsustainable patterns from causing burnout. Built by Rootly AI Labs and licensed under Apache License 2.0, On-Call Health integrates seamlessly with popular tools like PagerDuty, Rootly, Linear, GitHub, and Slack to aggregate signals from incident data, ticket workloads, after-hours activity, and communication patterns. This comprehensive view helps teams catch exhaustion early, before it turns into full-blown burnout.
The primary pain point On-Call Health addresses is the hidden overload that on-call engineers experience, which often goes undetected until burnout leads to retention issues. Traditional methods rely on subjective feedback and periodic check-ins, missing early warning signs such as gradual increases in incident frequency or after-hours contributions. On-Call Health provides objective signals that quantify on-call burden, allowing managers to spot overload before it spirals into burnout. Without such a tool, teams may fail to notice that an engineer has been handling an unusually high volume of incidents or negative sentiment until they are already disengaged. This data-driven approach converts subtle signals into actionable insights, making the case for operational improvements like rotation adjustments, automation investments, or pausing non-urgent projects. The result is a healthier, more sustainable on-call environment.
The first major feature group is 'Connect signals,' which enables On-Call Health to ingest incident data from Rootly or PagerDuty, ticket workload from Linear, after-hours signals from GitHub, and communication patterns from Slack. This integration creates a unified data pipeline without requiring manual data entry, automatically pulling relevant metrics. By aggregating these disparate sources, the tool provides a holistic picture of an engineer's on-call experience, revealing correlations between incident spikes, after-hours commits, and sentiment changes. For example, a sudden increase in GitHub activity outside normal hours combined with a rising incident count may indicate an unsustainable workload. This feature helps managers quickly identify which engineers are at risk, enabling targeted interventions before burnout occurs. It transforms raw data from multiple platforms into a coherent story of team health.
admin
The second major feature group encompasses 'Collect sentiment' and 'See who's at risk.' On-Call Health periodically sends short surveys directly in Slack, allowing on-call responders to share how they are doing with minimal friction. This sentiment collection is designed to reduce stigma by normalizing regular check-ins, making it safe for engineers to express stress or fatigue. The gathered data feeds into the risk scoring system, which computes individual risk scores on a scale of 0-100: 0-24 indicates healthy balance, 25-49 signals monitor risk, 50-74 calls for early intervention, and 75-100 demands immediate action. These scores are based on team and individual-specific baselines rather than fixed thresholds, ensuring fairness across different roles and workloads. The combination of qualitative sentiment and quantitative risk metrics gives a nuanced view of each engineer's health, highlighting both objective data and subjective experience.
The third major feature group is 'Act early with confidence,' powered by AI analysis that identifies what changed and what is driving the risk. On-Call Health's AI provides summaries that help stakeholders quickly get up to speed on trends they may have missed, turning weekly incident reviews into conversations about not just system reliability but also the people behind them. Managers can see which factors—like increased incidents, after-hours commits, or negative sentiment—are contributing most to a rising risk score. Additionally, the tool offers team-level risk factor trends, enabling proactive measures such as rebalancing rotations, adding automation, pausing non-urgent work, or staffing up. These AI-driven insights empower data-backed decision-making, reducing reliance on gut feelings and ensuring that interventions are targeted and timely.
On-Call Health operates through a straightforward workflow that starts with connecting your existing tools via the integration dashboard. Once connected, the tool continuously ingests data from Rootly, PagerDuty, Linear, GitHub, and Slack, and periodically prompts responders to share sentiment via Slack surveys. The system then computes risk scores for each individual using personalized baselines, tracking trends over time. AI analyzes the aggregated data to highlight significant changes and their probable causes. Users can view dashboards showing team and individual risk factors, trends, and AI-summarized insights. The entire process is designed to be low-friction, leveraging tools already in use, so teams can start monitoring on-call health without additional overhead. This workflow ensures that actionable insights are available in real time, enabling rapid response to emerging risks.
Concrete use cases for On-Call Health include a scenario where an engineering manager notices a rising risk score for a senior engineer who has been handling an increasing number of incidents. Using the tool, they see that the risk is driven by after-hours GitHub activity and negative sentiment from Slack surveys. They decide to rebalance the on-call rotation, add more automation for incident response, and pause non-urgent projects for that engineer. The outcome is a reduction in risk score and improved morale, preventing potential burnout. Another use case is during weekly incident reviews, where the AI summary helps a cross-functional team quickly understand that a recent spike in incidents is concentrated on a few individuals, prompting a discussion about staffing and tooling improvements. These outcomes demonstrate how On-Call Health turns data into actionable team improvements.
On-Call Health is targeted at engineering managers, infrastructure leads, DevOps teams, platform engineers, and incident response stakeholders who oversee on-call rotations. It is built on an open-source stack under Apache License 2.0, is free to use, and integrates with modern development and incident management platforms such as Rootly, PagerDuty, Linear, GitHub, and Slack. The tool is web-based with a focus on Slack integration for sentiment collection. Pricing is free with no paid tiers mentioned, making it accessible to teams of all sizes. In summary, On-Call Health provides an objective, data-driven way to detect on-call burnout detection, enabling teams to catch exhaustion early and protect their most valuable asset—their engineers. By making on-call health measurable and fair, it empowers teams to build sustainable operational practices.
Engineering managers, infrastructure leads, DevOps engineers, platform engineers, and incident response stakeholders who oversee on-call rotations and want to prevent engineer burnout using objective data. CTOs and VP of Engineering can use On-Call Health to get a high-level view of team health and make data-driven decisions about resource allocation. Additionally, individual on-call engineers benefit from reduced stigma around reporting fatigue through anonymous sentiment surveys. The tool is designed for teams using modern incident management tools like PagerDuty, Rootly, Linear, GitHub, and Slack, and is especially useful for organizations experiencing rapid growth that strains on-call capacity.