prometheus2 job from prometheus/26.4.0
Github source:
0550ced
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
prometheus
¶
alert_relabel_configs
¶Alerting relabel configuration
alertmanager
¶
notification_queue_capacity
¶The capacity of the queue for pending alert manager notifications
timeout
¶Timeout for sending alerts to Alertmanager
custom_rules
¶Array of custom alerting and recording rules
evaluation_interval
¶How frequently to evaluate rules by default
external_labels
¶Attach these labels to any time series or alerts when communicating with external systems
log_format
¶Output format of log messages. One of: [logfmt, json]
log_level
¶Only log messages with the given severity or above. One of: [debug, info, warn, error]
query
¶
lookback_delta
¶The delta difference allowed for retrieving metrics during expression evaluations
max_concurrency
¶Maximum number of queries executed concurrently
max_samples
¶Maximum number of samples a single query can load into memory
timeout
¶Maximum time a query may take before being aborted
remote_read
¶Remote read storage configuration
remote_write
¶Remote write storage configuration
rule_files
¶Array of paths to Prometheus rule files
rules
¶
alert
¶
for_grace_period
¶Minimum duration between alert and restored ‘for’ state
for_outage_tolerance
¶Max time to tolerate prometheus outage for restoring ‘for’ state of alert
resend_delay
¶Minimum amount of time to wait before resending an alert to Alertmanager
scrape_configs
¶Array of scrape configurations
scrape_interval
¶How frequently to scrape targets by default
scrape_timeout
¶How long until a scrape request times out
storage
¶
remote
¶
flush_deadline
¶How long to wait flushing sample on shutdown or config reload
read_concurrent_limit
¶Maximum number of concurrent remote read calls
read_max_bytes_in_frame
¶Maximum number of bytes in a single frame for streaming remote read response types before marshalling
read_sample_limit
¶Maximum overall number of samples to return via the remote read interface, in a single query
tsdb
¶
max_block_duration
¶Maximum duration compacted blocks may span (defaults to 10% of the retention period)
min_block_duration
¶Minimum duration of a data block before being persisted
no_lockfile
¶Do not create lockfile in data directory
- Default
false
retention
¶size
¶[Experimental]: Maximum number of bytes that storage blocks can use, oldest data will be removed first. Units supported: KB, MB, GB, PB. Ex: ‘512MB’
time
¶How long to retain samples in the storage
wal_compression
¶Compress the tsdb WAL
- Default
false
web
¶
console
¶
libraries
¶Path to the console library directory
- Default
/var/vcap/packages/prometheus2/bin/console_libraries
templates
¶Path to the console template directory, available at /consoles
- Default
/var/vcap/packages/prometheus2/bin/consoles
cors_origin
¶Regex for CORS origin
enable_admin_api
¶Enables API endpoints for admin control actions
- Default
false
enable_lifecycle
¶Enable shutdown and reload via HTTP request
- Default
false
external_url
¶The URL under which Prometheus is externally reachable
max_connections
¶Maximum number of simultaneous connections
page_title
¶Document title of Prometheus instance
port
¶Port to listen on for the web interface, API, and telemetry
- Default
"9090"
read_timeout
¶Maximum duration before timing out read of the request, and closing idle connections
route_prefix
¶Prefix for the internal routes of web endpoints
user_assets
¶Path to static asset directory, available at /user
Templates¶
Templates are rendered and placed onto corresponding
instances during the deployment process. This job's templates
will be placed into /var/vcap/jobs/prometheus2/
directory
(learn more).
bin/pre-start
(frombin/pre-start.erb
)bin/prometheus_ctl
(frombin/prometheus_ctl
)config/custom.rules.yml
(fromconfig/custom.rules.yml
)config/prometheus.yml
(fromconfig/prometheus.yml
)config/remote_write_ca.crt
(fromconfig/remote_write_ca.crt
)
Packages¶
Packages are compiled and placed onto corresponding
instances during the deployment process. Packages will be
placed into /var/vcap/packages/
directory.