Isn't it amazing that PagerDuty hasn't jumped on the AI band wagon to do things like this themselves? It seems they're leaving the door open to let in all the new oncall platforms into the market: incident.io, Firehydrant Signals, Rootly, ... Perhaps someone from PagerDuty will see this and buy your tool. It seems like exactly the kind of simple and immediate help on needs when responding to an incident, to have the biggest impact in resolving the incident quickly without redoing a bunch of work someone already did for an almost identical incident last week.

I've been putting together another oncall improvement, for a completely different area: making the scheduling of oncall work better (oncallscheduler.com). I'm trying to get feedback from people who work oncall about: 1. Is the scheduling of oncall work a significant pain point, and worth making more fair, predictable, and controllable by everybody. 2. Does the solution oncallscheduler.com is built on make sense? If you can spare a few mins, I would love it if you sent any thoughts to kristian@timewesp.com.

Hey HN,

The wife and I are both devs, and we both agreed that being on-call is probably the worst part of the job.

We decided to build something to try and make on-call issues a bit faster to deal with.

Basically Pandem.dev is a tool that you add to your company's Slack channel and it responds with useful information whenever an on-call ping comes in.

We basically index all previous incidents and when any new on-call tickets come in from Pagerduty, it'll respond with a list of related past issues.

We're also working on allowing the model to be trained on your on-call runbooks and docs, so it can suggest solutions and starting steps to diagnose or debug whenever a new issue comes up.

Let me know what you think, any feedback is appreciated!