Project

General

Profile

Actions

action #122848

closed

openQA Project - coordination #109846: [epic] Ensure all our database tables accomodate enough data, e.g. bigint for ids

coordination #113674: [epic] Configure I/O alerts again for the webui after migrating to the "unified alerting" in grafana size:M

Configure grouped alerts in Grafana correctly size:M

Added by livdywan almost 2 years ago. Updated over 1 year ago.

Status:
Resolved
Priority:
Low
Assignee:
Category:
-
Target version:
Start date:
2023-01-09
Due date:
% Done:

0%

Estimated time:
Tags:

Description

Summary

The migration in #112845 introduces repeating panels as well as a new concept 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

Related issues 3 (0 open3 closed)

Related to openQA Infrastructure - action #138044: Grouped seemingly unrelated alert emails are confusing size:MRejectedokurz2023-10-09

Actions
Related to openQA Infrastructure - action #159639: [alert] "web UI: Too many 5xx HTTP responses alert" size:SResolveddheidler2024-04-26

Actions
Blocked by openQA Infrastructure - action #122845: Migrate our Grafana setup to "unified alerting"Resolvednicksinger2023-01-09

Actions
Actions

Also available in: Atom PDF