bosh_exporter job from prometheus/29.1.0
Github source:
9cf244cd
or
master branch
Properties¶
bosh_exporter
¶
bosh
¶
ca_cert
¶BOSH CA Certificate
log_level
¶BOSH Log Level (‘DEBUG’, ‘INFO’, ‘WARN’, ‘ERROR’, ‘NONE’)
password
¶BOSH Password
uaa
¶
client_id
¶BOSH UAA Client ID
client_secret
¶BOSH UAA Client Secret
url
¶BOSH URL
username
¶BOSH Username
filter
¶
azs
¶Comma separated AZs to filter
cidrs
¶Comma separated CIDR to filter instance IPs
collectors
¶Comma separated collectors to filter (‘Deployments’, ‘Jobs’)
deployments
¶Comma separated deployments to filter
log_format
¶Set the log target and format. Example: ‘logger:syslog?appname=bob&local=7’ or ‘logger:stdout?json=true’
log_level
¶Only log messages with the given severity or above. Valid levels: [debug, info, warn, error, fatal]
metrics
¶
environment
¶Environment label to be attached to metrics
namespace
¶Metrics Namespace
sd
¶
processes_regexp
¶Regexp to filter Service Discovery processes names
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
"9190"
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/bosh_exporter/
directory
(learn more).
bin/bosh_exporter_ctl
(frombin/bosh_exporter_ctl
)config/bosh_ca_cert.pem
(fromconfig/bosh_ca_cert.pem
)config/web_tls_cert.pem
(fromconfig/web_tls_cert.pem
)config/web_tls_key.pem
(fromconfig/web_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.