News for hackers. Stuff that matters.

sylvainkalache

sylvainkalache on Hacker News

Show HN: On-Call Health – spot burnout before it hits your engineers

Posted by sylvainkalache on Thursday March 12, 2026 @03:12PM
from the show-hn dept.

https://github.com/Rootly-AI-Labs/On-Call-Health

We built On-Call Health because our industry has gotten very good at keeping systems healthy, but does little for the engineers on call managing them.On-call can be rough: 97% of engineers experience stress during incidents, 87% after, and 56% experience sleep disruption even without getting paged.We integrate with devtools like Rootly, PagerDuty, Linear, Jira, and Slack (for self-reported...

( Read More... | no comments | 2 points | on HN )
Re:The future of software engineering is SRE on Monday January 26, 2026 @12:59PM (#46769122)
If the future of software engineering is SRE, because GenAI is taking care of coding, a similar trend is coming for SRE-type work.

It's called AI SRE, and for now, it's mostly targeted at helping on-call engineers investigate and solve incidents. But of course, these agents can also be used proactively to improve reliability.

Re:Ask HN: What Are You Working On? (Nov 2025) on Tuesday November 11, 2025 @09:21AM (#45887575)
A tool that detects potential signs of overwork in incident responders, which could lead to burnout. To compute a per-responder risk score, it integrates with Rootly, PagerDuty, GitHub, and Slack.

We offer both a hosted version (https://oncallburnout.com/) and a self-hosted one (https://github.com/Rootly-AI-Labs/On-Call-Burnout-Detector).

Re:Ask HN: Why are most status pages delayed? on Tuesday November 04, 2025 @05:30PM (#45816621)
In my experience as a former SRE currently working for an incident management SaaS (Rootly).

Two main reasons: 1) The status page update is not automated. It takes time for the incident management process to go through all the steps and updating the status page is generally not the first one. It's often an overlooked one.

2) The company would rather not communicate that they are/were down, or they are not yet sure of the impact, and therefore don't yet have the correct information to share.

Of course, all modern incident platforms will offer tools to update your page super easily/in real-time. But tooling is generally not the main issue; it's process/information.

Re:Ask HN: What are you working on? (September 2025) on Monday September 29, 2025 @05:37PM (#45419069)
A burnout detector for SREs. The goal is to help teams identify incident responders who may be overworked/getting burned out.

We are looking at:

-Objective data: signals from incident management tools (Rootly/PagerDuty), GitHub, and Slack

-Self-reported data: asking the engineers how they feel via short survey

From this, we generate a CBI score (Copenhagen Burnout Inventory). We're still in beta, but we've received positive feedback from our beta testers, especially from manager of large and distributed orgs.

It's fully open-source, you can test it out locally https://github.com/Rootly-AI-Labs/rootly-burnout-detector-we...

Alternatively, we offer a hosted version with mock data, allowing you to play with it. https://www.oncallburnout.com/

If you have any feedback or ideas, shoot them my way :)

Re:Apple Photos App Corrupts Images on Thursday September 18, 2025 @06:56AM (#45288102)
Same here. They have a known bugs where entries will vanish from your contacts. Data loss is a big deal (or so I thought).

Support asked me to let them know when a contact vanishing did so they could gather logs from me phone.

Once I was finally able to see it happen, I reached out. Reported that it had just happened overnight. The customer support said it was too long of a time frame for engineers to investigate because "it generates a lot of logs and that's too much to go through". I could not believe their answer.

I just moved my contacts to Gmail and that was the end of it.

Older »