consul_exporter icon indicating copy to clipboard operation
consul_exporter copied to clipboard

Exporter for Consul metrics

Results 53 consul_exporter issues
Sort by recently updated
recently updated
newest added

We are thinking of implementing this in our environments to get an overview of the services in consul, and have a few questions with regards to that: 1. How often...

Currently, consul_exporter exposes both catalogue KV and service tags via `consul_service_tag`. Registered services in consul can also expose metadata which is a KV structure but without the special meaning of...

This extends the exporter to collect everything exposed by the https://www.consul.io/api-docs/operator/autopilot#read-health endpoint. Naming is weird, but I wanted to call out that this isn't something that should typically be collected...

stale

as title says, i can't find dashboard .json from grafana.com .

enhancement
help wanted
hacktoberfest

**What did you do?** Ran consul_exporter with the following: ./consul_exporter --web.listen-address=":9107" --consul.health-summary --consul.server="http://localhost:8500" --consul.require_consistent **What did you expect to see?** Reads to be consistent **What did you see instead? Under...

enhancement
help wanted

Hello Would you accept a patch that adds consul_kv_bool with booleans in consul matched to 0/1 metrics? Thanks

help wanted

Hi, I saw one of your previous issue https://github.com/prometheus/consul_exporter/issues/133 where the response you have given is by increasing the timeout for consul while getting service health, but increase in timeout...

In the 'Using Docker' section at [Docker Hub](https://hub.docker.com/r/prom/consul-exporter), the suggested docker run command still uses a hyphen **-consul.server** flag, when in reality a dash is needed (--).

Adds the IP address label to the metrics. Our use case is that since many of our nodes are not yet hooked up to consul, our alerting/visualization tools are tied...

stale

As discussed in #45, I've added service tags as a separate metric. One tag per series. I've done the same with node metadata. One key/value pair per series.

stale