shield_exporter job from prometheus/21.1.0
Github source:
75e3e4b
or
master branch
Properties¶
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
shield_exporter
¶
filter
¶
collectors
¶Comma separated collectors to filter. If not set, all collectors will be enabled (‘Archives’, ‘Jobs’, ‘RetentionPolicies’, ‘Schedules’, ‘Status’, ‘Stores’, ‘Targets’, ‘Tasks’)
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
shield
¶
backend_url
¶Shield Backend URL
password
¶Shield Password
skip_ssl_verify
¶Disable Shield SSL Verify
trace
¶Enable Shield trace mode
username
¶Shield Username
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
"9179"
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)
Templates¶
Templates are rendered and placed onto corresponding
instances during the deployment process. This job's templates
will be placed into /var/vcap/jobs/shield_exporter/
directory
(learn more).
bin/shield_exporter_ctl
(frombin/shield_exporter_ctl
)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.