forked from mehdiBezahaf/intent-deploy
-
Notifications
You must be signed in to change notification settings - Fork 0
/
alertmanager.yml
55 lines (45 loc) · 1.39 KB
/
alertmanager.yml
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
# global:
# The smarthost and SMTP sender used for mail notifications.
# # The root route on which each incoming alert enters.
route:
receiver: default
group_wait: 30s
group_interval: 5m
# 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" ]
# # 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, cluster, service ]
receivers:
- name: default
webhook_configs:
- url: "http://web:8080/alert"
http_config:
basic_auth:
username: webhook
password_file: /tmp/webhook_pass
# - name: 'team-X-mails'
# email_configs:
# - to: '[email protected]'
# - name: 'team-X-pager'
# email_configs:
# - to: '[email protected]'
# pagerduty_configs:
# - service_key: <team-X-key>
# - name: 'team-Y-mails'
# email_configs:
# - to: '[email protected]'
# - name: 'team-Y-pager'
# pagerduty_configs:
# - service_key: <team-Y-key>
# - name: 'team-DB-pager'
# pagerduty_configs:
# - service_key: <team-DB-key>