stackdriver_exporter job from prometheus/29.2.0
Github source:
2aaef0fc
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
stackdriver_exporter
¶
collector
¶
fill_missing_labels
¶Fill missing metrics labels with empty string to avoid label dimensions inconsistent failure
- Default
false
application_credentials
¶Google JSON key
project_id
¶Comma seperated list of Google Project IDs
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]
monitoring
¶
drop_delegated_projects
¶Drop metrics from attached projects and fetch
project_id
only
- Default
false
metrics_interval
¶Interval to request the Google Stackdriver Monitoring Metrics for
metrics_offset
¶Offset for the Google Stackdriver Monitoring Metrics interval into the past
metrics_type_prefixes
¶Comma separated Google Stackdriver Monitoring Metric Type prefixes
stackdriver
¶
backoff_jitter
¶The amount of jitter to introduce in a exp backoff scenario
http_timeout
¶How long should stackdriver_exporter wait for a result from the Stackdriver API
max_backoff
¶Max time between each request in an exp backoff scenario
max_retries
¶Max number of retries that should be attempted on 503 errors from stackdriver
retry_statuses
¶The HTTP statuses that should trigger a retry
web
¶
port
¶Port on which to expose web interface and telemetry
- Default
"9255"
telemetry_path
¶Path under which to expose Prometheus 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/stackdriver_exporter/
directory
(learn more).
bin/stackdriver_exporter_ctl
(frombin/stackdriver_exporter_ctl
)config/goole_application_credentials.json
(fromconfig/goole_application_credentials.json
)
Packages¶
Packages are compiled and placed onto corresponding
instances during the deployment process. Packages will be
placed into /var/vcap/packages/
directory.