Add a ScrapeConfig for blackbox probes using GCE discovery
Split from #2680 (closed)
As part of our goal to scrape the same Prometheus Jobs that the VMs do from the Prometheus remote agents. On this particular issue will be focus in on the fluentd exporter - prometheus job
Original configuration in chef for the job, (see chef role https://gitlab.com/gitlab-com/gl-infra/chef-repo/-/blob/master/roles/gprd-infra-prometheus-server.json)
They are many jobs for the blackbox probes, please see the config above. In production we've the following jobs
- blackbox (58 / 58 active targets)
- blackbox-data (1 / 1 active targets)
- blackbox-elastic-monitoring-es7-health (1 / 1 active targets)
- blackbox-elastic-monitoring-es7-ilm (1 / 1 active targets)
- blackbox-elastic-monitoring-es7-ilm-status (1 / 1 active targets)
- blackbox-elastic-prod-health (1 / 1 active targets)
- blackbox-elastic-prod-ilm (1 / 1 active targets)
- blackbox-elastic-prod-ilm-status (1 / 1 active targets)
- blackbox-internal (1 / 1 active targets)
- blackbox-kas-426 (2 / 2 active targets)
- blackbox-ssh (4 / 4 active targets)
- blackbox-tls-expiry (45 / 45 active targets)
- blackbox-tls-redirect (12 / 12 active targets)
- blackbox-tls-upgrade (18 / 18 active targets)
- blackbox-with-auth (9 / 9 active targets)
- blackbox_exporter (1 / 1 active targets)
This issue will be about add the relevant ScrapeConfig
using the GCE discovery to scrape the blackbox probes
At the moment, there is not a clear place to write this scrape configuration, I will follow up with a ticket that will allow us to give home to this and other similar configurations.
You can add the relevant configuration to the helm chart https://gitlab.com/gitlab-com/gl-infra/charts/-/tree/main/gitlab/prometheus-agent