@intentius/chant-lexicon-prometheus 0.97.0 → 0.99.0

package/src/import/testdata/upstream/alertmanager-simple.yml

@@ -0,0 +1,130 @@
+# Vendored from github.com/prometheus/alertmanager v0.34.1, doc/examples/simple.yml
+# (https://github.com/prometheus/alertmanager/blob/v0.34.1/doc/examples/simple.yml). Apache-2.0.
+# Unchanged below this header.
+global:
+  # The smarthost and SMTP sender used for mail notifications.
+  smtp_smarthost: 'localhost:25'
+  smtp_from: 'alertmanager@example.org'
+  smtp_auth_username: 'alertmanager'
+  smtp_auth_password: 'password'
+
+# The directory from which notification templates are read.
+templates:
+  - '/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: ['alertname', 'cluster', 'service']
+
+  # 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: team-X-mails
+
+  # All the above attributes are inherited by all child routes and can
+  # 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.
+    - matchers:
+        - 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:
+        - matchers:
+            - severity="critical"
+          receiver: team-X-pager
+    - matchers:
+        - service="files"
+      receiver: team-Y-mails
+
+      routes:
+        - matchers:
+            - 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.
+    - matchers:
+        - service="database"
+      receiver: team-DB-pager
+      # Also group alerts by affected database.
+      group_by: [alertname, cluster, database]
+      routes:
+        - matchers:
+            - owner="team-X"
+          receiver: team-X-pager
+          continue: true
+        - matchers:
+            - 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_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: '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>
+
+tracing:
+  endpoint: localhost:4317
+  insecure: true
+  sampling_fraction: 1.0

package/src/import/testdata/upstream/alertmanager-sns-topic-arn.yml

@@ -0,0 +1,17 @@
+# Vendored from github.com/prometheus/alertmanager v0.34.1, config/testdata/conf.sns-topic-arn.yml
+# (https://github.com/prometheus/alertmanager/blob/v0.34.1/config/testdata/conf.sns-topic-arn.yml). Apache-2.0.
+# Unchanged below this header.
+route:
+  receiver: 'sns-api-notifications'
+  group_by: [alertname]
+receivers:
+  - name: 'sns-api-notifications'
+    sns_configs:
+      - api_url: https://sns.us-east-2.amazonaws.com
+        topic_arn: arn:aws:sns:us-east-2:123456789012:My-Topic
+        sigv4:
+          region: us-east-2
+          access_key: access_key
+          secret_key: secret_ket
+        attributes:
+          severity: Sev2

package/src/import/testdata/upstream/alertmanager-telegram-default-bot-token-file.yml

@@ -0,0 +1,16 @@
+# Vendored from github.com/prometheus/alertmanager v0.34.1, config/testdata/conf.telegram-default-bot-token-file.yml
+# (https://github.com/prometheus/alertmanager/blob/v0.34.1/config/testdata/conf.telegram-default-bot-token-file.yml). Apache-2.0.
+# Unchanged below this header.
+global:
+  telegram_bot_token_file: /global_file
+route:
+  receiver: team-X-telegram
+
+receivers:
+  - name: team-X-telegram
+    telegram_configs:
+      - chat_id: 123
+  - name: team-Y-telegram
+    telegram_configs:
+      - chat_id: 456
+        bot_token_file: /override_file

package/src/import/testdata/upstream/alertmanager-victorops-default-apikey-file.yml

@@ -0,0 +1,23 @@
+# Vendored from github.com/prometheus/alertmanager v0.34.1, config/testdata/conf.victorops-default-apikey-file.yml
+# (https://github.com/prometheus/alertmanager/blob/v0.34.1/config/testdata/conf.victorops-default-apikey-file.yml). Apache-2.0.
+# Unchanged below this header.
+global:
+  victorops_api_key_file: '/global_file'
+route:
+  group_by: ['alertname', 'cluster', 'service']
+  group_wait: 30s
+  group_interval: 5m
+  repeat_interval: 3h
+  receiver: team-Y-victorops
+  routes:
+    - match:
+        service: foo
+      receiver: team-X-victorops
+receivers:
+  - name: 'team-X-victorops'
+    victorops_configs:
+      - routing_key: 'team-X'
+  - name: 'team-Y-victorops'
+    victorops_configs:
+      - routing_key: 'team-Y'
+        api_key_file: /override_file

package/src/import/testdata/upstream/alertmanager-wechat-default-api-secret-file.yml

@@ -0,0 +1,18 @@
+# Vendored from github.com/prometheus/alertmanager v0.34.1, config/testdata/conf.wechat-default-api-secret-file.yml
+# (https://github.com/prometheus/alertmanager/blob/v0.34.1/config/testdata/conf.wechat-default-api-secret-file.yml). Apache-2.0.
+# Unchanged below this header.
+global:
+  wechat_api_secret_file: '/global_file'
+  wechat_api_corp_id: 'my_corp_id'
+route:
+  receiver: 'wechat-notifications'
+  group_by: [alertname, datacenter, app]
+receivers:
+  - name: 'wechat-notifications'
+    wechat_configs:
+      # Use global
+      - {}
+      # Override global with other file
+      - api_secret_file: '/override_file'
+      # Override global with inline API secret
+      - api_secret: 'my_inline_secret'

package/src/import/testdata/upstream/prometheus-alerting-rules.yml

@@ -0,0 +1,15 @@
+# From github.com/prometheus/prometheus v3.15.0, docs/configuration/alerting_rules.md,
+# "Defining alerting rules" (https://github.com/prometheus/prometheus/blob/v3.15.0/docs/configuration/alerting_rules.md). Apache-2.0.
+groups:
+- name: example
+  labels:
+    team: myteam
+  rules:
+  - alert: HighRequestLatency
+    expr: job:request_latency_seconds:mean5m{job="myjob"} > 0.5
+    for: 10m
+    keep_firing_for: 5m
+    labels:
+      severity: page
+    annotations:
+      summary: High request latency

package/src/import/testdata/upstream/prometheus-alerting-templates.yml

@@ -0,0 +1,23 @@
+# From github.com/prometheus/prometheus v3.15.0, docs/configuration/alerting_rules.md,
+# "Templating" example (https://github.com/prometheus/prometheus/blob/v3.15.0/docs/configuration/alerting_rules.md). Apache-2.0.
+groups:
+- name: example
+  rules:
+
+  # Alert for any instance that is unreachable for >5 minutes.
+  - alert: InstanceDown
+    expr: up == 0
+    for: 5m
+    labels:
+      severity: page
+    annotations:
+      summary: "Instance {{ $labels.instance }} down"
+      description: "{{ $labels.instance }} of job {{ $labels.job }} has been down for more than 5 minutes."
+
+  # Alert for any instance that has a median request latency >1s.
+  - alert: APIHighRequestLatency
+    expr: api_http_request_latencies_second{quantile="0.5"} > 1
+    for: 10m
+    annotations:
+      summary: "High request latency on {{ $labels.instance }}"
+      description: "{{ $labels.instance }} has a median request latency above 1s (current value: {{ $value }}s)"

package/src/import/testdata/upstream/prometheus-recording-rules.yml

@@ -0,0 +1,7 @@
+# From github.com/prometheus/prometheus v3.15.0, docs/configuration/recording_rules.md,
+# "A simple example rules file" (https://github.com/prometheus/prometheus/blob/v3.15.0/docs/configuration/recording_rules.md). Apache-2.0.
+groups:
+  - name: example
+    rules:
+    - record: code:prometheus_http_requests_total:sum
+      expr: sum by (code) (prometheus_http_requests_total)