Is there a suggested method for monitoring the health of consul agents to catch instances that haven't joined the consul cluster, or have left but not rejoined?
Our Prometheus deployment uses Consul for service discovery and primarily monitors infrastructure on AWS. My current thinking is that we should use EC2 service discovery to enumerate instances and scrape an exporter on some predefined port that exposes metrics that indicate whether consul is up and whether it has joined a cluster. Is that a sane approach, or am I thinking of this the wrong way?
If my thinking is correct, should I be deploying the regular consul exporter for this purpose? It seems like it's intended to be run only on consul servers, not on regular agents[0] and it exports quite a few metrics which aren't meaningful in the agent context. Is support for a flag that exposes only agent-specific metrics something that would be considered if I put in a PR, or would that be best left to a separate consul_agent_exporter?