| 1 |
# See https://prometheus.io/docs/alerting/latest/configuration/ for details. |
| 2 |
|
| 3 |
global: |
| 4 |
# The smarthost and SMTP sender used for mail notifications. |
| 5 |
smtp_smarthost: "mailhog:1025" |
| 6 |
smtp_from: "[email protected]" |
| 7 |
smtp_require_tls: false |
| 8 |
|
| 9 |
receivers: |
| 10 |
- name: "team-X" |
| 11 |
email_configs: |
| 12 |
- to: "[email protected]" |
| 13 |
send_resolved: true |
| 14 |
|
| 15 |
# The root route on which each incoming alert enters. |
| 16 |
route: |
| 17 |
# The labels by which incoming alerts are grouped together. For example, |
| 18 |
# multiple alerts coming in for cluster=A and alertname=LatencyHigh would |
| 19 |
# be batched into a single group. |
| 20 |
group_by: ["alertname", "cluster", "service"] |
| 21 |
|
| 22 |
# When a new group of alerts is created by an incoming alert, wait at |
| 23 |
# least 'group_wait' to send the initial notification. |
| 24 |
# This way ensures that you get multiple alerts for the same group that start |
| 25 |
# firing shortly after another are batched together on the first |
| 26 |
# notification. |
| 27 |
group_wait: 30s |
| 28 |
|
| 29 |
# When the first notification was sent, wait 'group_interval' to send a batch |
| 30 |
# of new alerts that started firing for that group. |
| 31 |
group_interval: 5m |
| 32 |
|
| 33 |
# If an alert has successfully been sent, wait 'repeat_interval' to |
| 34 |
# resend them. |
| 35 |
repeat_interval: 3h |
| 36 |
|
| 37 |
# A default receiver |
| 38 |
receiver: team-X |
| 39 |
|
| 40 |
# All the above attributes are inherited by all child routes and can |
| 41 |
# overwritten on each. |
| 42 |
|
| 43 |
# The child route trees. |
| 44 |
routes: |
| 45 |
# This route matches error alerts created from spans or logs. |
| 46 |
- matchers: |
| 47 |
- alert_kind="error" |
| 48 |
group_interval: 24h |
| 49 |
receiver: team-X |
| 50 |
|
| 51 |
# The directory from which notification templates are read. |
| 52 |
templates: |
| 53 |
- "/etc/alertmanager/template/*.tmpl" |