Exporter output when pacemaker is down about ha_cluster_exporter HOT 7 CLOSED

(@stefanotorresi maybe we could think to don't raise an error if we have 0 collectors and just do nothing)

This is how it was before, and we deemed it was very unpredictable as a behaviour. If there are no services to introspect, then the exporter will fail outright so that the up metric reports the failure; there is no point in having the exporter still running without exporting anything.

from ha_cluster_exporter.

@oxedions The exporter itself will report a metric exposing with the collector could collect the data or not: https://github.com/ClusterLabs/ha_cluster_exporter/blob/master/doc/metrics.md#ha_cluster_scrape_success. Also, if Prometheus cannot scrap some target, like the exporter is not reachable, it will also report a metric called UP (see: https://prometheus.io/docs/concepts/jobs_instances/). On both cases, you can create alerts based on these metrics.

from ha_cluster_exporter.

hi @oxedions nice question and valid remarks 👍

1. by design the ha_cluster_exporter if pacemaker or any collector is down, it will not gather and expose the metrics.

This is

we raise/error only if 0 collector are registered. (@stefanotorresi maybe we could think to don't raise an error if we have 0 collectors and just do nothing)

2. regarding point 2 so basically if you have other components before the pacemaker collector is running, you should be able to do it.

Also in case if node 1 for some reason, right now the 2nd exporter can catch this

Let me know if it helps.

Dario

from ha_cluster_exporter.

Dear @MalloZup , Dear @diegoakechi , Dear @MalloZup ,

So I can monitor ha_cluster_scrape_success, this is the value I was looking for.

By default, I start the ha_exporter at boot, and not corrosync/pacemaker, which is why I forked your service file.
I am doing that because the exporter, in our configuration, is expected to run anytime, even if nothing is exported (having nothing exported, i.e. ha_cluster_scrape_success = 0 but ha_cluster = up is also an interesting value for us: means HA cluster is down for a reason, but exporter is still alive, so no need to worry about the exporter, only check HA).

Many thanks for these answers 😊
And many thanks for the exporter and the dashboard.

from ha_cluster_exporter.

Well, in fact we do start the ha_exporter in a clone resource now.

from ha_cluster_exporter.

I guess I can close this then. ✌️

from ha_cluster_exporter.

Yes, thanks a lot ! 😊

from ha_cluster_exporter.