-
Notifications
You must be signed in to change notification settings - Fork 168
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
additional metrics #29
Comments
Unfortunately, these metrics aren't exposed via the Consul HTTP or RPC APIs. Currently, the only way to get them into Prometheus is using the statsd_exporter. |
There is a long standing issue for providing all metrics over a HTTP API: hashicorp/consul#817. At SoundCloud we have a side-car next to every consul agent which queries serf and other stats via the consul ctl / rpc interface and exposes it via Prometheus. |
Some consistency would indeed be good. |
This has been resolved in hashicorp/consul#3369 More metrics are now exposed through the |
hi, or if it is possible only with statsd, do you have YAML-based config format of this config |
Recent versions of Consul support the Prometheus exposition natively (see https://www.consul.io/docs/agent/options#telemetry-prometheus_retention_time) so this doesn't need to be reimplemented in the exporter IMHO. |
Hello,
Would there be a possibility to add the following metrics to the exported data?
consul.consul.leader.reconcile.count
consul.serf.events.consul_new_leader
It's based on this article I found regarding consul monitoring.
It does makes sense
The text was updated successfully, but these errors were encountered: