Page MenuHomeSoftware Heritage

Allow icinga checks to write prometheus metrics files
ClosedPublic

Authored by vsellier on May 17 2022, 8:24 PM.

Details

Summary

The prometheus data are readable by everyone so adding icinga in
the prometheus groups seems to not open any hole

Related to T3129

Test Plan
  • pergamon (collected resources not visible)
diff origin/production/pergamon.softwareheritage.org current/pergamon.softwareheritage.org
*******************************************
+ File[/var/lib/prometheus/node-exporter] =>
   parameters =>
     "ensure": "directory",
     "group": "prometheus",
     "mode": "0775",
     "owner": "prometheus"
*******************************************
*** End octocatalog-diff on pergamon.softwareheritage.org

Diff Detail

Repository
rSPSITE puppet-swh-site
Lint
Automatic diff as part of commit; lint not applicable.
Unit
Automatic diff as part of commit; unit tests not applicable.

Event Timeline

ardumont added inline comments.
site-modules/profile/manifests/icinga2/objects/e2e_checks_base.pp
8

I'm having a hard-time reading this, what does this mean?

Add groups prometheus to user nagios?

site-modules/profile/manifests/icinga2/objects/e2e_checks_base.pp
8

yep exactly
I used this notation because when I try to configure the group via a user or a group class, puppet complains about duplicate declaration which makes sens.

This revision is now accepted and ready to land.May 18 2022, 2:36 PM