Change Details

Currently we have an haproxy exporter that we scrape with prometheus to extract haproxy stats, but since haproxy 2.0.0 it ships with it's own internal metrics endpoint: See https://github.com/prometheus/haproxy_exporter for details We should move to that internal endpoint instead and avoid the extra process. As the stats are named differently, a proposed action plan is: * [] move all the current users of haproxy_exporter to **also** collect haproxy stats * [] notify teams that the stats changed * [] remove the scraping of all the haproxy_exporter and set `profile::haproxy_exporter::enable` to `absent` to uninstall/stop * [] cleanup the haproxy_exporter entries once puppet ran everywhere Note that we would be collecting duplicated stats for some time until we move everyone to the haproxy internal metrics.

Currently we have an haproxy exporter that we scrape with prometheus to extract haproxy stats, but since haproxy 2.0.0 it ships with it's own internal metrics endpoint: See https://github.com/prometheus/haproxy_exporter for details We should move to that internal endpoint instead and avoid the extra process. As the stats are named differently, a proposed action plan is: * [] move all the current users of haproxy_exporter to **also** collect haproxy stats ** Thumbor is moving itself soon, so no patches needed there ** Toolforge elasticsearch uses haproxy<2, so no stats, might want to upgrade first * [] notify teams that the stats changed * [] remove the scraping of all the haproxy_exporter and set `profile::haproxy_exporter::enable` to `absent` to uninstall/stop * [] cleanup the haproxy_exporter entries once puppet ran everywhere Note that we would be collecting duplicated stats for some time until we move everyone to the haproxy internal metrics.

Currently we have an haproxy exporter that we scrape with prometheus to extract haproxy stats, but since haproxy 2.0.0 it ships with it's own internal metrics endpoint: See https://github.com/prometheus/haproxy_exporter for details We should move to that internal endpoint instead and avoid the extra process. As the stats are named differently, a proposed action plan is: * [] move all the current users of haproxy_exporter to **also** collect haproxy stats ** Thumbor is moving itself soon, so no patches needed there ** Toolforge elasticsearch uses haproxy<2, so no stats, might want to upgrade first * [] notify teams that the stats changed * [] remove the scraping of all the haproxy_exporter and set `profile::haproxy_exporter::enable` to `absent` to uninstall/stop * [] cleanup the haproxy_exporter entries once puppet ran everywhere Note that we would be collecting duplicated stats for some time until we move everyone to the haproxy internal metrics.