About two years ago I ran into several issues with Grafana OnCall in practice:
- alert flapping caused numerous unnecessary incidents to be created
- the architecture (5 components) felt unnecessarily complex
- managing large routing trees via the UI was difficult
So I decided to build IMPulse to be IaC-ready, with Alertmanager-like routing and a single-component architecture to simplify operations for DevOps teams.
The first working version took about 3 months and already solved the problems we had internally. Later another contributor joined the project, and now IMPulse is a standalone project and we're continuing to improve it.
Hi HN! I'm the author of IMPulse.
About two years ago I ran into several issues with Grafana OnCall in practice:
- alert flapping caused numerous unnecessary incidents to be created
- the architecture (5 components) felt unnecessarily complex
- managing large routing trees via the UI was difficult
So I decided to build IMPulse to be IaC-ready, with Alertmanager-like routing and a single-component architecture to simplify operations for DevOps teams.
The first working version took about 3 months and already solved the problems we had internally. Later another contributor joined the project, and now IMPulse is a standalone project and we're continuing to improve it.
GitHub: https://github.com/eslupmi/impulse
Docs: https://docs.impulse.bot
Happy to answer questions!