Open AliArtukov opened 5 months ago
Thanks for opening this issue. A team member should give feedback soon. In the meantime, feel free to check out the contributing guidelines.
Hi, I would like to work on this.
I've strolled through the codebase here and seen relevant PR's like the implementation of opsgenie and sns. I have also tested the telegram API a bit and know what to do. However, the signoz fork of alertmanager predates that of the prometheus telegram implementation. So maybe there is potential for some improvement if that's alright.
An idea for a better workflow is to make a group/supergroup and make the bot admin there. Hence, users can join and leave relevant groups for alerts requiring less hands-on management with each chat_id
. This comes at basically zero cost since both(individual and group) are chat_id
. It's also more practical if multiple people are in a group so they can coordinate actions via chat there itself. I'm not sure who uses Telegram for devops but wouldn't be surprised if there are teams in eastern Europe who use it seriously in such situations.
cc @srikanthccv
Add Telegram Bot to the list of alert channels. Use only Bot API Token and Chat ID for configuring channel. Grafana used telegram bot for sending notifications (https://grafana.com/blog/2023/12/28/how-to-integrate-grafana-alerting-and-telegram/).