Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Better grafana to Slack alerts #153

Open
rgaudin opened this issue Dec 16, 2023 · 1 comment
Open

Better grafana to Slack alerts #153

rgaudin opened this issue Dec 16, 2023 · 1 comment
Labels
enhancement New feature or request

Comments

@rgaudin
Copy link
Member

rgaudin commented Dec 16, 2023

With grafana, we now have access to alerts on HTTP 50x errors (on for all 50x) and one for 500 on all our containers. It's a good thing but the way we get those alerts is not ideal:

  • we get a message after a varying delay of up to 5mn
  • we get a resolved message once the grafana condition for alert is gone.
  • the messages are very long and useless, with just the namespace burried inside the extended version of the message

The most annoying to me is the resolve message that creates noise. The fact that I have to switch context to go to slack, select channel and click on the message to find out about the namespace (and infer the culprit container) may look like nothing to care about but it's actually a huge blocker to react on issues.

Uptime robot alerts very clear and useful in comparison. From the notification preview I already know what's going on an can decide whether it requires immediate action or not.

With grafana, I can't so I mostly decide that I'll look at it when I get a chance…

Screenshot 2023-12-16 at 14 30 24
Screenshot 2023-12-16 at 14 30 41
Screenshot 2023-12-16 at 14 30 51
@rgaudin rgaudin added the enhancement New feature or request label Dec 16, 2023
@benoit74
Copy link
Collaborator

I can only agree 👍

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

2 participants