ansible-taler-exchange

Ansible playbook to deploy a production Taler Exchange
Log | Files | Refs | Submodules | README | LICENSE

alertmanager.yml (2611B)

      1 # Sample configuration.
      2 # See https://prometheus.io/docs/alerting/configuration/ for documentation.
      3 
      4 global:
      5   # The smarthost and SMTP sender used for mail notifications.
      6   smtp_smarthost: 'firefly.gnunet.org:25'
      7   smtp_from: 'alertmanager@taler.net'
      8   smtp_require_tls: false
      9     #smtp_auth_username: 'alertmanager'
     10     #smtp_auth_password: 'password'
     11 
     12 # The directory from which notification templates are read.
     13 templates:
     14 - '/etc/prometheus/alertmanager_templates/*.tmpl'
     15 
     16 # The root route on which each incoming alert enters.
     17 route:
     18   # The labels by which incoming alerts are grouped together. For example,
     19   # multiple alerts coming in for cluster=A and alertname=LatencyHigh would
     20   # be batched into a single group.
     21   group_by: ['alertname', 'cluster', 'service']
     22 
     23   # When a new group of alerts is created by an incoming alert, wait at
     24   # least 'group_wait' to send the initial notification.
     25   # This way ensures that you get multiple alerts for the same group that start
     26   # firing shortly after another are batched together on the first
     27   # notification.
     28   group_wait: 30s
     29 
     30   # When the first notification was sent, wait 'group_interval' to send a batch
     31   # of new alerts that started firing for that group.
     32   group_interval: 5m
     33 
     34   # If an alert has successfully been sent, wait 'repeat_interval' to
     35   # resend them.
     36   repeat_interval: 12h
     37 
     38   # A default receiver
     39   receiver: taler-warning-mails
     40 
     41   # All the above attributes are inherited by all child routes and can
     42   # overwritten on each.
     43 
     44   # The child route trees.
     45   routes:
     46   - matchers:
     47     - severity = critical
     48     receiver: taler-admin-mails
     49 
     50 
     51 # Inhibition rules allow to mute a set of alerts given that another alert is
     52 # firing.
     53 # We use this to mute any warning-level notifications if the same alert is
     54 # already critical.
     55 inhibit_rules:
     56 - source_match:
     57     severity: 'critical'
     58   target_match:
     59     severity: 'warning'
     60   # Apply inhibition if the alertname is the same.
     61   equal: ['alertname', 'cluster', 'service']
     62 
     63 
     64 receivers:
     65 - name: 'taler-warning-mails'
     66   email_configs:
     67   - to: 'warnings@taler.net'
     68 - name: 'taler-admin-mails'
     69   email_configs:
     70   - to: 'sysadmin@taler.net'
     71     #
     72     #- name: 'team-X-pager'
     73     #  email_configs:
     74     #  - to: 'team-X+alerts-critical@example.org'
     75     #  pagerduty_configs:
     76     #  - service_key: <team-X-key>
     77     #
     78     #- name: 'team-Y-mails'
     79     #  email_configs:
     80     #  - to: 'team-Y+alerts@example.org'
     81     #
     82     #- name: 'team-Y-pager'
     83     #  pagerduty_configs:
     84     #  - service_key: <team-Y-key>
     85     #
     86     #- name: 'team-DB-pager'
     87     #  pagerduty_configs:
     88     #  - service_key: <team-DB-key>