2021-02-13 11:38:38 -08:00
|
|
|
# Copyright (c) 2018-2021, diyIT.org
|
2020-02-25 11:28:31 -08:00
|
|
|
# All rights reserved.
|
|
|
|
|
#
|
|
|
|
|
# BSD 2-Clause License ("Simplified BSD License" or "FreeBSD License")
|
|
|
|
|
# https://diyit.org/license/
|
|
|
|
|
#
|
|
|
|
|
#
|
|
|
|
|
|
|
|
|
|
global:
|
|
|
|
|
# The smarthost and SMTP sender used for mail notifications.
|
|
|
|
|
smtp_smarthost: 'mail.ahlawat.com:25'
|
|
|
|
|
smtp_from: 'sharad@ahlawat.com'
|
|
|
|
|
smtp_hello: 'monitor.ahlawat.com'
|
|
|
|
|
|
|
|
|
|
# The directory from which notification templates are read.
|
|
|
|
|
templates:
|
|
|
|
|
- '/usr/local/etc/alertmanager/template/*.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.
|
|
|
|
|
#
|
|
|
|
|
# To aggregate by all possible labels use '...' as the sole label name.
|
|
|
|
|
# This effectively disables aggregation entirely, passing through all
|
|
|
|
|
# alerts as-is. This is unlikely to be what you want, unless you have
|
|
|
|
|
# a very low alert volume or your upstream notification system performs
|
|
|
|
|
# its own grouping. Example: group_by: [...]
|
|
|
|
|
group_by: ['...']
|
|
|
|
|
|
|
|
|
|
# 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: admin-email
|
|
|
|
|
|
|
|
|
|
# All the above attributes are inherited by all child routes and can
|
|
|
|
|
# overwritten on each.
|
|
|
|
|
|
|
|
|
|
# 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: 'admin-email'
|
|
|
|
|
email_configs:
|
|
|
|
|
- to: 'sharad@diyit.org'
|
|
|
|
|
send_resolved: true
|
