Open Sourcing IT Incident Management System
medium.comWe're excited to introduce our new open source incident management system! It's designed to help teams handle incidents quickly and efficiently. With features like automated incident response, real-time notifications, and a comprehensive incident history, it's never been easier to keep your team informed and on top of potential issues. Learn more about our incident management system and its features on our website and see how it can help streamline your incident management process.
Official Website - https://harpia.io/
https://github.com/harpia-io/harpia
AGPL, as seems to be fashionable in infrastructure projects of late
You have a broken link in your readme: https://github.com/harpia-io/harpia/blob/master/README.md?pl...
and `git add .` is a mind poison: https://github.com/harpia-io/harp-daemon/tree/master/harp_da... (not just that repo, those pycache dirs are in all the ones I looked at)
Thank you!
I have fixed both issues
Why does the arrow only go to PagerDuty and not from it? I imagine there's already integrations that initiate an incident via PD so it could be managed from this system. Going only to PD means it has to be managed downstream, recreated in the system or migrate all integrations from PD to an intermediary which seems unwise as it's another failure point.
With the arrows the way they are, I would think that this is more of an incident filtering and initiator than management with a people-perspective. My memory's fuzzy but I recall something like that for SNMP traps, maybe called NetView.