alertmanager job from prometheus/23.2.0

Github source: f29fb3a or master branch

Properties¶

alertmanager¶

alerts¶

gc_interval¶

Interval between alert GC

cluster¶

gossip_interval¶

Interval between sending gossip messages. By lowering this value (more frequent) gossip messages are propagated across the cluster more quickly at the expense of increased bandwidth

peer_timeout¶

Time to wait between peers to send notifications

port¶

Cluster listen port

Default

9094

probe_interval¶

Interval between random node probes. Setting this lower (more frequent) will cause the cluster to detect failed nodes more quickly at the expense of increased bandwidth usage

probe_timeout¶

Timeout to wait for an ack from a probed node before assuming it is unhealthy. This should be set to 99-percentile of RTT (round-trip time) on your network

pushpull_interval¶

Interval for gossip state syncs. Setting this interval lower (more frequent) will increase convergence speeds across larger clusters at the expense of increased bandwidth usage

reconnect_interval¶

Interval between attempting to reconnect to lost peers

reconnect_timeout¶

Length of time to attempt to reconnect to a lost peer

settle_timeout¶

Maximum time to wait for cluster connections to settle before evaluating notifications

tcp_timeout¶

Timeout for establishing a stream connection with a remote node for a full state sync, and for stream read and write operations

data¶

retention¶

How long to keep data for

hipchat¶

auth_token¶

The AuthToken to use for Hipchat notifications

url¶

The URL to use for Hipchat notifications

http_config¶

Set global Alertmanager HTTP Config

inhibit_rules¶

Inhibition rules

log_level¶

Only log messages with the given severity or above. Valid levels: [debug, info, warn, error, fatal]

mesh¶

port¶

Deprecated. Please use alertmanager.cluster.port

opsgenie¶

api_host¶

The API Host to use for OpsGenie notifications

api_key¶

The OpsGenie API Key

pagerduty¶

url¶

The URL to use for PagerDuty notifications

receivers¶

Receivers

resolve_timeout¶

ResolveTimeout is the time after which an alert is declared resolved if it has not been updated

route¶

continue¶

Whether an alert should continue matching subsequent sibling nodes

group_by¶

The labels by which incoming alerts are grouped together

group_interval¶

How long to wait before sending notification about new alerts that are in are added to a group of alerts for which an initial notification has already been sent

group_wait¶

How long to initially wait to send a notification for a group of alerts

match¶

A set of equality matchers an alert has to fulfill to match the node

match_re¶

A set of regex-matchers an alert has to fulfill to match the node

receiver¶

default receiver

repeat_interval¶

How long to wait before sending a notification again if it has already been sent successfully for an alert

routes¶

Child routes

slack¶

api_url¶

The API URL to use for Slack notifications

smtp¶

auth_identity¶

SMTP authentication identity

auth_password¶

SMTP authentication password

auth_secret¶

SMTP authentication secret

auth_username¶

SMTP authentication username

from¶

The default SMTP From header field

require_tls¶

SMTP TLS requirement

smarthost¶

The default SMTP smarthost used for sending emails

templates¶

Array of file paths from which custom notification template definitions are read

test_alert¶

daily¶

Send a test alert daily?

Default

false

hourly¶

Send a test alert hourly?

Default

false

weekly¶

Send a test alert weekly?

Default

false

victorops¶

api_key¶

VictorOps API key

api_url¶

VictorOps API URL

web¶

external_url¶

The URL under which Alertmanager is externally reachable

port¶

Port to listen on for the web interface and API

Default

"9093"

route_prefix¶

Prefix for the internal routes of web endpoints

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/alertmanager/ directory (learn more).

• bin/alertmanager_ctl (from bin/alertmanager_ctl)
• bin/alertmanager_test (from bin/alertmanager_test)
• bin/pre-start (from bin/pre-start)
• config/alertmanager.yml (from config/alertmanager.yml)

Packages¶

Packages are compiled and placed onto corresponding instances during the deployment process. Packages will be placed into /var/vcap/packages/ directory.

• alertmanager