58 lines
1.8 KiB
Django/Jinja
58 lines
1.8 KiB
Django/Jinja
# {{ ansible_managed }}
|
|
|
|
global:
|
|
# The smarthost and SMTP sender used for mail notifications.
|
|
smtp_smarthost: 'proxy.auro.re:25'
|
|
smtp_from: 'prometheus@auro.re'
|
|
#smtp_auth_username: 'alertmanager'
|
|
#smtp_auth_password: 'password'
|
|
smtp_require_tls: false
|
|
|
|
# The directory from which notification templates are read.
|
|
templates:
|
|
- '/etc/prometheus/alertmanager_templates/*.tmpl'
|
|
|
|
# The root route on which each incoming alert enters.
|
|
route:
|
|
# The labels by which incoming alerts are grouped together. For example,
|
|
# multiple alerts coming in for cluster=A and alertname=LatencyHigh would
|
|
# be batched into a single group.
|
|
group_by: ['alertname', 'cluster', 'service']
|
|
|
|
# When a new group of alerts is created by an incoming alert, wait at
|
|
# least 'group_wait' to send the initial notification.
|
|
# This way ensures that you get multiple alerts for the same group that start
|
|
# firing shortly after another are batched together on the first
|
|
# notification.
|
|
group_wait: 30s
|
|
|
|
# When the first notification was sent, wait 'group_interval' to send a batch
|
|
# of new alerts that started firing for that group.
|
|
group_interval: 5m
|
|
|
|
# If an alert has successfully been sent, wait 'repeat_interval' to
|
|
# resend them.
|
|
repeat_interval: 3h
|
|
|
|
# A default receiver
|
|
receiver: team-monitoring-mails
|
|
|
|
|
|
# Inhibition rules allow to mute a set of alerts given that another alert is
|
|
# firing.
|
|
# We use this to mute any warning-level notifications if the same alert is
|
|
# already critical.
|
|
inhibit_rules:
|
|
- source_match:
|
|
severity: 'critical'
|
|
target_match:
|
|
severity: 'warning'
|
|
# Apply inhibition if the alertname is the same.
|
|
equal: ['alertname', 'cluster', 'service']
|
|
|
|
|
|
receivers:
|
|
- name: 'team-monitoring-mails'
|
|
email_configs:
|
|
- to: 'monitoring.aurore@lists.crans.org'
|
|
|