Page MenuHomeSoftware Heritage

prometheus: Support http parameters in exporter configuration
ClosedPublic

Authored by vsellier on Aug 12 2021, 3:50 PM.

Details

Summary

2 commits:


It's needed for promox monitoring because it uses a metric url like
/pve?target=host

The parameters can't be put directly on the metric_path configuration

Related to T3462


prometheus/pve_exporter: Split the metrics_path and the parameters

Related to T3462


Test Plan
  • uffizi
diff origin/production/uffizi.internal.softwareheritage.org current/uffizi.internal.softwareheritage.org
*******************************************
  Profile::Prometheus::Export_scrape_config[pve-exporter_uffizi.internal.softwareheritage.org] =>
   parameters =>
     metrics_path =>
      - /pve?target=127.0.0.1
      + /pve
     params =>
      + {"target"=>["127.0.0.1"]}
*******************************************
*** End octocatalog-diff on uffizi.internal.softwareheritage.org
  • pergamon
diff origin/production/pergamon.softwareheritage.org current/pergamon.softwareheritage.org
*******************************************
  File[/usr/local/bin/update-prometheus-config] =>
   parameters =>
     content =>
      - {md5}761580a6e029c82c61bdc37f46270c46
      + {md5}34059150b195fb497afe67d494c51d12
*******************************************
*** End octocatalog-diff on pergamon.softwareheritage.org
  • there are no changes nodes that are not hypervisors

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.