action #122848
Updated by cdywan 3 months ago
# Summary
The migration in #112845 introduces repeating panels as well as a new concept concetpt of grouped alerts. We should know how that impacts existing alert handling and potentially take advantage of it where beneficial.
## Acceptance criteria
* **AC1:** grouping of alerts is properly configured and understood
## Suggestions
* Look into alert grouping
* Confirm that alert group is what we think it is
* Monitor alert emails and see how they can be affected by grouping
* Figure out how to avoid multiple redundant alert emails e.g. several emails like `[FIRING:1] (Failed systemd services alert (except openqa)` about the same issue (the alert was only in the state "Alerting" once on the day we've got the redundant mails) with no changes in-between OR confirm if there was a change that's somehow not reflected in the email
The migration in #112845 introduces repeating panels as well as a new concept concetpt of grouped alerts. We should know how that impacts existing alert handling and potentially take advantage of it where beneficial.
## Acceptance criteria
* **AC1:** grouping of alerts is properly configured and understood
## Suggestions
* Look into alert grouping
* Confirm that alert group is what we think it is
* Monitor alert emails and see how they can be affected by grouping
* Figure out how to avoid multiple redundant alert emails e.g. several emails like `[FIRING:1] (Failed systemd services alert (except openqa)` about the same issue (the alert was only in the state "Alerting" once on the day we've got the redundant mails) with no changes in-between OR confirm if there was a change that's somehow not reflected in the email