> Blackbox exporter does have a /metrics endpoint, but this is only for
> metrics internal to the operation of blackbox_exporter itself (e.g.
> memory stats, software version). You don't need to scrape this, but it
> gives you a little bit of extra info about how your exporter is
> performing.
The reason I suggested scraping Blackbox's /metrics endpoint was as a
convenient way to create an up{} metric that reflects whether or not
Blackbox itself is up. You can do this with the up{} metrics of
individual probes, but if you use them either you need to pick a
specific probe target that you know will always be present or you need
to aggregate the up{} metrics of probes together, so that if N% of them
go to 0 you can raise an alert. (I failed to explain this at all well in
my original message.)
(Depending on how you do Blackbox relabeling, your up{} metrics from
probes may not have a label that identifies the Blackbox instance. Now
that I look, our metrics don't, which may be something I want to fix.)
If all your Blackbox targets are generated through dynamic service
discovery, it might be possible for your service discovery to break so
that you have no probes and thus no up{} metrics generated from them.
Although at this point it's probably unimportant whether Blackbox itself
is up, since you likely have bigger problems.
- cks
--
You received this message because you are subscribed to the Google Groups
"Prometheus Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
To view this discussion on the web visit
https://groups.google.com/d/msgid/prometheus-users/466805.1701192090%40apps0.cs.toronto.edu.
