Skip to content

cf_exporter job from prometheus/29.7.0

Github source: af7e95f or master branch

Properties

cf_exporter

cf

api_url

Cloud Foundry API URL

client_id

Cloud Foundry Client ID

client_secret

Cloud Foundry Client Secret

deployment_name

Cloud Foundry Deployment Name to be reported as a metric label

password

Cloud Foundry Password

username

Cloud Foundry Username

filter

collectors

Comma separated collectors to filter (Applications,Buildpacks,Events,IsolationSegments,Organizations,Routes,SecurityGroups,ServiceBindings,ServiceInstances,ServicePlans,Services,Spaces,Stacks), If not set, all collectors except Events are enabled.

log_level

Only log messages with the given severity or above. Valid levels: [debug, info, warn, error, fatal]

Default
info

log_stream

Set the log target stream ‘stdout’ or ‘stderr’

Default
stderr

metrics

environment

Environment label to be attached to metrics

namespace

Metrics Namespace

skip_ssl_verify

Disable SSL Verify

Default
false

web

auth_password

Password for web interface basic auth

auth_username

Username for web interface basic auth

port

Port on which to expose web interface and telemetry

Default
"9193"
telemetry_path

Path under which to expose Prometheus metrics

tls_cert

TLS certificate (PEM format). If the certificate is signed by a certificate authority, the file should be the concatenation of the server’s certificate, any intermediates, and the CA’s certificate

tls_key

TLS private key (PEM format)

env

http_proxy

HTTP proxy to use

https_proxy

HTTPS proxy to use

no_proxy

List of comma-separated hosts that should skip connecting to the proxy

Templates

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

  • config/bpm.yml (from bpm.yml.erb)
  • config/web_tls_cert.pem (from web_tls_cert.pem.erb)
  • config/web_tls_key.pem (from web_tls_key.pem.erb)

Packages

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