Merge "prometheus-alertmanager: yaml indentation fixes"

prometheus-alertmanager/values.yaml

@@ -180,7 +180,7 @@ conf:
       hipchat_api_url: 'https://hipchat.foobar.org/'
     # The directory from which notification templates are read.
     templates:
-    - '/etc/alertmanager/template/*.tmpl'
+      - '/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,
@@ -208,78 +208,79 @@ conf:
       # overwritten on each.
       # The child route trees.
       routes:
-      # This routes performs a regular expression match on alert labels to
-      # catch alerts that are related to a list of services.
-      - match_re:
-          service: ^(foo1|foo2|baz)$
-        receiver: team-X-mails
-        # The service has a sub-route for critical alerts, any alerts
-        # that do not match, i.e. severity != critical, fall-back to the
-        # parent node and are sent to 'team-X-mails'
-        routes:
+        # This routes performs a regular expression match on alert
+        # labels to catch alerts that are related to a list of
+        # services.
+        - match_re:
+            service: ^(foo1|foo2|baz)$
+          receiver: team-X-mails
+          # The service has a sub-route for critical alerts, any alerts
+          # that do not match, i.e. severity != critical, fall-back to the
+          # parent node and are sent to 'team-X-mails'
+          routes:
+            - match:
+                severity: critical
+              receiver: team-X-pager
         - match:
-            severity: critical
-          receiver: team-X-pager
-      - match:
-          service: files
-        receiver: team-Y-mails
-        routes:
+            service: files
+          receiver: team-Y-mails
+          routes:
+            - match:
+                severity: critical
+              receiver: team-Y-pager
+        # This route handles all alerts coming from a database service. If there's
+        # no team to handle it, it defaults to the DB team.
         - match:
-            severity: critical
-          receiver: team-Y-pager
-      # This route handles all alerts coming from a database service. If there's
-      # no team to handle it, it defaults to the DB team.
-      - match:
-          service: database
-        receiver: team-DB-pager
-        # Also group alerts by affected database.
-        group_by:
-          - alertname
-          - cluster
-          - database
-        routes:
-        - match:
-            owner: team-X
-          receiver: team-X-pager
-        - match:
-            owner: team-Y
-          receiver: team-Y-pager
+            service: database
+          receiver: team-DB-pager
+          # Also group alerts by affected database.
+          group_by:
+            - alertname
+            - cluster
+            - database
+          routes:
+            - match:
+                owner: team-X
+              receiver: team-X-pager
+            - match:
+                owner: team-Y
+              receiver: team-Y-pager
     # 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
+      - source_match:
+          severity: 'critical'
+        target_match:
+          severity: 'warning'
+        # Apply inhibition if the alertname is the same.
+        equal:
+          - alertname
+          - cluster
+          - service
     receivers:
-    - name: 'team-X-mails'
-      email_configs:
-      - to: 'team-X+alerts@example.org'
-    - name: 'team-X-pager'
-      email_configs:
-      - to: 'team-X+alerts-critical@example.org'
-      pagerduty_configs:
-      - service_key: <team-X-key>
-    - name: 'team-Y-mails'
-      email_configs:
-      - to: 'team-Y+alerts@example.org'
-    - name: 'team-Y-pager'
-      pagerduty_configs:
-      - service_key: <team-Y-key>
-    - name: 'team-DB-pager'
-      pagerduty_configs:
-      - service_key: <team-DB-key>
-    - name: 'team-X-hipchat'
-      hipchat_configs:
-      - auth_token: <auth_token>
-        room_id: 85
-        message_format: html
-        notify: true
+      - name: 'team-X-mails'
+        email_configs:
+          - to: 'team-X+alerts@example.org'
+      - name: 'team-X-pager'
+        email_configs:
+          - to: 'team-X+alerts-critical@example.org'
+        pagerduty_configs:
+          - service_key: <team-X-key>
+      - name: 'team-Y-mails'
+        email_configs:
+          - to: 'team-Y+alerts@example.org'
+      - name: 'team-Y-pager'
+        pagerduty_configs:
+          - service_key: <team-Y-key>
+      - name: 'team-DB-pager'
+        pagerduty_configs:
+          - service_key: <team-DB-key>
+      - name: 'team-X-hipchat'
+        hipchat_configs:
+          - auth_token: <auth_token>
+            room_id: 85
+            message_format: html
+            notify: true
   alertmanager_templates: null