Skip to content

elasticsearch_exporter job from prometheus/28.0.0

Github source: 35ab18d9 or master branch

Properties

elasticsearch_exporter

es

all

Enable/disable exporting stats for all nodes in the cluster

Default
false
ca_cert

Trusted CA Certificate (PEM format) for the Elasticsearch connection

cluster_settings

Export stats for cluster settings

Default
false
clusterinfo
interval

Cluster info update interval for the cluster label

indices

Export stats for indices in the cluster

Default
false
indices_mappings

Export stats for mappings of all indices of the cluster

Default
false
indices_settings

Export stats for settings of all indices of the cluster

Default
false
node

Node’s name of which metrics should be exposed

shards

Export stats for shards in the cluster (implies –es.indices)

Default
false
snapshots

Export stats for the cluster snapshots

Default
false
ssl_skip_verify

Skip SSL verification when connecting to Elasticsearch

Default
false
timeout

Timeout for trying to get stats from Elasticsearch

tls_cert

TLS Certificate (PEM format) for the private key to connect to Elasticsearch

tls_key

TLS Private key (PEM format) for client auth when connecting to Elasticsearch

uri

HTTP API address of an Elasticsearch node

log_format

Sets the log format. Valid formats are json and logfmt

log_level

Sets the loglevel. Valid levels are debug, info, warn, error

web

port

Port on which to expose web interface and telemetry

Default
"9114"
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/elasticsearch_exporter/ directory (learn more).

  • bin/elasticsearch_exporter_ctl (from bin/elasticsearch_exporter_ctl)
  • config/es_ca_cert.pem (from config/es_ca_cert.pem)
  • config/es_tls_cert.pem (from config/es_tls_cert.pem)
  • config/es_tls_key.pem (from config/es_tls_key.pem)

Packages

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