Show IH: Incident Management in Slack Bot
Hello IH!
Inspiration given by this community was one of the reasons why I left my full-time DevOps job and started working on my own project. Thank you all for that 😊I've been a silent member for a while and now I'm happy to say: We have something to show! It's a Slack Bot for Incident Management called Amixr.IO.
This term "Incident Management" should be familiar for those who are doing DevOps professionally. For others, I'll try to explain it in simple words.
Imagine you have some monitoring tool (For example Grafana). This monitoring tool could send "Alerts" about Incidents in your system. Usually, Alerts are just simple push notifications in various channels.
If you are working on something critical that's not enough.
- Alert could just sneak between engineers attention and remain unresolved. That's a first problem Amixr solves. It will escalate Incident and trigger engineers one by one until someone will resolve it.
- Engineers like to receive alerts on different channels. One is ok using Slack, other prefers SMS. That's why we have multi-channel Alert delivery ✉️
I'll be really happy if you try and post some feedback here! Please let me know in case you use some unsupported monitoring tool. I'll be happy to add it for you ☺️
Just try adding it to your Slack Workspace: https://amixr.io/
🚀
Really cool! It is brave decision to start your own project 😮
Wish you good luck! Waiting for new posts 👌🏻
Thank you! 😊
This comment was deleted 7 years ago
Huge thank you for your feedback, Jason! You are right, we need to focus on the website a lot. Now it's just a place to store "Add to Slack" button. I expected the product to be self-explanatory and now I see it was naive.
About alerts from your infrastructure going to Amixr: it's simple. Amixr Bot just gives you a webhook endpoint. You add it to Grafana and that's it. Slack Bot is just an interface.
Integration with each alerting system is a huge work. Each of them has own philosophy and multiple small nuances we want to know and use properly. Now only Grafana and AlertManager are supported. As time goes we'll definitely integrate with all the systems you mentioned.
There is always a huge risk unknown SaaS will be unreliable and will make you problems. I'm pretty sure Amixr won't. Me and my partners are DevOps engineers with many years of experience in building and maintaining high-loaded and uptime-critical systems. Of course, we build Amixr using all our best efforts in infrastructure...
How do you think, what's the best thing to assure our users that Amixr is a reliable tool? I'm working on such updates for the website to fix this:
Stay tuned and thank you again :)