Page MenuHomePhorge
Files F117750171

alertmanager-configmap.yaml
No OneTemporary
Actions

Authored By
Unknown
Size
2 KB
Referenced Files
None
Subscribers
None

alertmanager-configmap.yaml
View Options

{{- if .Values.alertmanager.enabled -}}
kind: ConfigMap
apiVersion: v1
metadata:
name: alertmanager-config
data:
alertmanager.yaml: |
global:
smtp_smarthost: 'postfix:587'
smtp_from: 'alertmanager@{{ .Values.domainName }}'
smtp_auth_username: '{{ .Values.serviceAccounts.monitoring1.username }}'
smtp_auth_password: '{{ .Values.serviceAccounts.monitoring1.password }}'
route:
receiver: 'operations-team'
# 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: ['alertname']
# 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: 12h
routes:
- matchers:
- severity="none"
receiver: 'noone'
# 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_matchers:
- severity="critical"
target_matchers:
- severity=~"warning|info"
# Apply inhibition if the alertname is the same.
# CAUTION:
# If all label names listed in `equal` are missing
# from both the source and target alerts,
# the inhibition rule will apply!
equal: ['alertname']
receivers:
- name: 'operations-team'
email_configs:
- to: 'admin@{{ .Values.domainName }}'
headers:
- name: 'noone'
# To send notifications to noone
{{- end }}

File Metadata

Mime Type
text/plain
Expires
Sat, Apr 4, 2:08 AM (1 w, 2 d ago)
Storage Engine
local-disk
Storage Format
Raw Data
Storage Handle
cd/4a/95dc7a118f1a6026aeb3a4e6d20d
Default Alt Text
alertmanager-configmap.yaml (2 KB)

Event Timeline