cadvisor job from prometheus/18.2.0
Github source:
c921b694 or
master branch
Properties¶
cadvisor¶
allow_dynamic_housekeeping¶Whether to allow the housekeeping interval to be dynamic
application_metrics_count_limit¶Max number of application metrics to store (per container)
boot_id_file¶Comma-separated list of files to check for boot-id. Use the first one that exists
bq_account¶Service account email
bq_credentials¶Credential Key (pem)
bq_id¶Client ID
bq_project_id¶Bigquery project ID
bq_secret¶Client Secret
collector_cert¶Collector’s certificate, exposed to endpoints for certificate based authentication
collector_key¶Key for the collector’s certificate
container_hints¶Location of the container hints file
disable_metrics¶comma-separated list of metrics to be disabled. Options are ‘disk’, ‘network’, ‘tcp’
docker¶docker endpoint
docker_env_metadata_whitelist¶a comma-separated list of environment variable keys that needs to be collected for docker containers
docker_only¶Only report docker containers in addition to root stats
enable_load_reader¶Whether to enable cpu load reader
event_storage_age_limit¶Max length of time for which to store events (per type)
event_storage_event_limit¶Max number of events to store (per type)
global_housekeeping_interval¶Interval between global housekeepings
housekeeping_interval¶Interval between container housekeepings
http_auth¶HTTP auth for the web UI
http_auth_realm¶HTTP auth realm for the web UI
http_digest¶HTTP digest for the web UI
http_digest_realm¶HTTP digest file for the web UI
log_backtrace_at¶when logging hits line file:N, emit a stack trace (default :0)
log_cadvisor_usage¶Whether to log the usage of the cAdvisor container
machine_id_file¶Comma-separated list of files to check for machine-id. Use the first one that exists.
max_housekeeping_interval¶Largest interval to allow between container housekeepings
max_procs¶max number of CPUs that can be used simultaneously
port¶port to listen
- Default
8080
profiling¶Enable profiling via web interface host:port/debug/pprof/
prometheus_endpoint¶Endpoint to expose Prometheus metrics on
stderrthreshold¶logs at or above this threshold go to stderr
storage_driver¶Storage driver to use. Data is always cached shortly in memory, this controls where data is pushed besides the local cache. Empty means none
storage_driver_buffer_duration¶Writes in the storage driver will be buffered for this duration, and committed to the non memory backends as a single transaction
storage_driver_db¶database name
storage_driver_es_enable_sniffer¶ElasticSearch uses a sniffing process to find all nodes of your cluster by default, automatically
storage_driver_es_host¶ElasticSearch host:port
storage_driver_es_index¶ElasticSearch index name
storage_driver_es_type¶ElasticSearch type name
storage_driver_host¶database host:port
storage_driver_kafka_broker_list¶kafka broker(s) csv
storage_driver_kafka_ssl_ca¶optional certificate authority for TLS client authentication
storage_driver_kafka_ssl_cert¶optional certificate for TLS client authentication
storage_driver_kafka_ssl_key¶optional key for TLS client authentication
storage_driver_kafka_ssl_verify¶verify ssl certificate chain
storage_driver_kafka_topic¶kafka topic
storage_driver_password¶database password
storage_driver_secure¶use secure connection with database
storage_driver_table¶table name
storage_driver_user¶database username
storage_duration¶How long to keep data stored
v¶log level for V logs
vmodule¶comma-separated list of pattern=N settings for file-filtered logging
Templates¶
Templates are rendered and placed onto corresponding
instances during the deployment process. This job's templates
will be placed into /var/vcap/jobs/cadvisor/ directory
(learn more).
bin/cadvisor_ctl(frombin/cadvisor_ctl)config/bq_credentials.pem(fromconfig/bq_credentials.pem)config/http_auth(fromconfig/http_auth)config/http_digest(fromconfig/http_digest)config/kafka_ssl_ca.pem(fromconfig/kafka_ssl_ca.pem)config/kafka_ssl_cert.pem(fromconfig/kafka_ssl_cert.pem)config/kafka_ssl_key.pem(fromconfig/kafka_ssl_key.pem)
Packages¶
Packages are compiled and placed onto corresponding
instances during the deployment process. Packages will be
placed into /var/vcap/packages/ directory.