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

[BUG] When alerts are grouped, the card does not differentiate between status firing and resolved #344

Open
bvanelli opened this issue Sep 8, 2023 · 0 comments
Labels
bug Something isn't working

Comments

@bvanelli
Copy link

bvanelli commented Sep 8, 2023

Describe the bug

This happens because of an (oversight?) on alertmanager. It apparently groups the messages to send them all at once, but there can be entries which are resolved in between those messages:

{
   "alert":{
      "receiver":"prometheus-msteams",
      "status":"firing",
      "alerts":[
         {
            "status":"resolved",
            "labels":{
...

If at least one status is firing, then the whole alert status is set to firing. And since they are grouped in the same message and this "status" is not provided as label, it will then display on the default template as triggering, when in fact it isn't.

There is some discussion on the prometheus repo I'll also link:

prometheus/alertmanager#2334 (comment)

Version

Using latest 1.3.4

To Reproduce

Maybe I can craft an example request to reproduce it later.

Expected behavior

It should either:

  • Remove the resolved from the list when displaying the alert or
  • Even better, separate the alerts into two distinct messages, so that one of them only shows the still firing and the other the

Screenshots
If applicable, add screenshots to help explain your problem.

Additional context
Add any other context about the problem here.

@bvanelli bvanelli added the bug Something isn't working label Sep 8, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

1 participant