Skip to content

Adjust prometheus alert rules to exclude repro4

The newly added rebuilder from !927 (merged) is still not excluded from certain alerts which leads to a bad signal-to-noise ratio in my inbox:

   1       25/03/03 11:15AM alertmanager@ar [RESOLVED] repro4.pkgbuild.com warning (HostHighCpuLoad) (9.8K)
   2       25/03/03 11:00AM alertmanager@ar [FIRING:1] repro4.pkgbuild.com warning (HostHighCpuLoad) (9.8K)
   5       25/03/03 01:31AM alertmanager@ar [RESOLVED] repro4.pkgbuild.com warning (HostHighCpuLoad) (9.8K)
   6       25/03/03 12:31AM alertmanager@ar [FIRING:1] repro4.pkgbuild.com warning (HostHighCpuLoad) (9.8K)

This would just require a few small tweaks to https://gitlab.archlinux.org/archlinux/infrastructure/-/blob/master/roles/prometheus/files/node.rules.yml.

While we're added we could also generalize the (already regex'ed) rule to an actual regex like "repro.*pkgbuild.com".

Edited by Christian Heusel
To upload designs, you'll need to enable LFS and have an admin enable hashed storage. More information