Skip to content

consul_exporter job from prometheus/30.3.0

Github source: d0e6d65 or master branch

Properties

consul_exporter

consul_allow_stale

Allows any Consul server (non-leader) to service a read

Default
false

consul_ca

PEM-encoded certificate authority used to validate the authenticity of a server certificate

consul_cert

PEM-encoded certificate used with the private key to verify the exporter’s authenticity

consul_health_summary

Generate a health summary for each service instance. Needs n+1 queries to collect all information

Default
false

consul_insecure

Disable TLS host verification

consul_key

PEM-encoded private key used with the certificate to verify the exporter’s authenticity

consul_request_limit

Limit the maximum number of concurrent requests to consul, 0 means no limit

consul_require_consistent

Forces the read to be fully consistent

Default
false

consul_server

HTTP API address of a Consul server or agent

consul_server_name

When provided, this overrides the hostname for the TLS certificate. It can be used to ensure that the certificate name matches the hostname we declare

consul_timeout

Timeout on HTTP requests to consul

kv_filter

Regex that determines which keys to expose

kv_prefix

Prefix from which to expose key/value pairs

log_format

Output format of log messages. One of: [logfmt, json]

log_level

Only log messages with the given severity or above. One of: [debug, info, warn, error]

web

port

Port on which to expose web interface and telemetry

Default
"9107"
telemetry_path

Path under which to expose metrics

Templates

Templates are rendered and placed onto corresponding instances during the deployment process. This job's templates will be placed into /var/vcap/jobs/consul_exporter/ directory (learn more).

  • bin/consul_exporter_ctl (from bin/consul_exporter_ctl)
  • config/consul_ca.pem (from config/consul_ca.pem)
  • config/consul_cert.pem (from config/consul_cert.pem)
  • config/consul_key.pem (from config/consul_key.pem)

Packages

Packages are compiled and placed onto corresponding instances during the deployment process. Packages will be placed into /var/vcap/packages/ directory.