News for hackers. Stuff that matters.
Re:Show HN: I built an open-source tool to make on-call suck... by sanj001 on Sunday July 28, 2024 @05:57PM (#41096275)
Using LLMs to classify noisy alerts is a really clever approach to tackling alert fatigue! Are you fine tuning your own model to differentiate between actionable and noisy alerts?

I'm also working on an open source incident management platform called Incidental (https://github.com/incidentalhq/incidental), slightly orthogonal to what you're doing, and it's great to see others addressing these on-call challenges.

Our tech stacks are quite similar too - I'm also using Python 3, FastAPI!

Re:Show HN: I built an open-source tool to make on-call suck... by aray07 on Sunday July 28, 2024 @06:23PM (#41096426)
Thanks for the feedback! I saw the incidental launch on HN and have been following your journey!
Re:Show HN: I built an open-source tool to make on-call suck... by jobtemp on Sunday July 28, 2024 @06:09PM (#41096349)
Why not use statistics? Been reading about xmr charts recently on commoncog. That might help for example.
Re:Show HN: I built an open-source tool to make on-call suck... by Jolter on Monday July 29, 2024 @03:37AM (#41098567)
I wouldn’t say it’s particularly clever. It’s a fairly obvious idea to anyone who has worked with alerting through IMs. What it is, is /difficult/, because you really really need to avoid false positives. Probably lots of hard work involved. So kudos for making this work (if it works)!
Re:Show HN: I built an open-source tool to make on-call suck... by david1542 on Monday July 29, 2024 @10:19AM (#41100672)
I'm curious about incidental :) how are you going to compete with other, well established IM tools like rootly, incident.io, firehydrant.com?