Datasets:

openenvforge
/

3ambench

#!/bin/bash
# oracle: rewrites changed files to the oracle state
set -euo pipefail
cd /workspace/monitoring
mkdir -p 'alertmanager'
cat > 'alertmanager/alertmanager.yml' <<'AF_EOF'
# Shared Alertmanager config (this repo, platform and data Prometheus servers).
# Receivers belong to the teams; ask before touching someone else's.
global:
  resolve_timeout: 5m
  slack_api_url_file: /etc/alertmanager/secrets/slack-url
templates:
- /etc/alertmanager/templates/*.tmpl
route:
  receiver: slack-alerts-default
  group_by: [alertname, service]
  group_wait: 30s
  group_interval: 5m
  repeat_interval: 4h
  routes:
  # rule evaluation problems. Nobody pages on these (yet).
  - matchers:
    - alertname=~"PrometheusRuleFailures|PrometheusRuleEvaluationSlow"
    receiver: slack-prometheus-meta
  # SRE sees every page as FYI; owners get paged by their own subtree below.
  - matchers:
    - severity=~"page|critical"
    receiver: slack-sre-fyi
    continue: true
  - matchers:
    - team="payer-integrations"
    receiver: slack-payer-integrations
    routes:
    - matchers:
      - severity=~"page|critical"
      receiver: pagerduty-payer-integrations
      continue: true
    - matchers:
      - severity="ticket"
      receiver: jira-payer-integrations
      continue: true
    - receiver: slack-payer-integrations
  - matchers:
    - team="clinical-ops"
    receiver: slack-clinical-ops
    routes:
    - matchers:
      - severity=~"page|critical"
      receiver: pagerduty-clinical-ops
      continue: true
    - matchers:
      - severity="ticket"
      receiver: jira-clinical-ops
      continue: true
    - receiver: slack-clinical-ops
  - matchers:
    - team="member-experience"
    receiver: slack-member-experience
    routes:
    - matchers:
      - severity=~"page|critical"
      receiver: pagerduty-member-experience
      continue: true
    - matchers:
      - severity="ticket"
      receiver: jira-member-experience
      continue: true
    - receiver: slack-member-experience
  # provider-data: still on the old match syntax
  - match:
      team: provider-data
    receiver: slack-provider-data
    routes:
    - match_re:
        severity: page|critical
      receiver: pagerduty-provider-data
      continue: true
    - match:
        severity: ticket
      receiver: jira-provider-data
      continue: true
    - receiver: slack-provider-data
  - matchers:
    - team="claims"
    receiver: slack-claims-oncall
    routes:
    - matchers:
      - severity=~"page|critical"
      receiver: pagerduty-claims
      continue: true
    - matchers:
      - severity="ticket"
      receiver: jira-claims
      continue: true
    - receiver: slack-claims-oncall
  # member-experience services from before team labels were everywhere
  - matchers:
    - service=~"member-api"
    receiver: slack-member-experience
    routes:
    - matchers:
      - severity=~"page|critical"
      receiver: pagerduty-member-experience
      continue: true
    - receiver: slack-member-experience
  - matchers:
    - team="eligibility"
    receiver: slack-eligibility
    routes:
    - matchers:
      - severity=~"page|critical"
      receiver: pagerduty-eligibility
      continue: true
    - matchers:
      - severity="ticket"
      receiver: jira-eligibility
      continue: true
    - receiver: slack-eligibility
  # teams below route alerts from the platform and data Prometheus servers
  - matchers:
    - team="network"
    receiver: slack-network
    group_interval: 10m
    routes:
    - matchers:
      - severity=~"page|critical"
      receiver: pagerduty-network
      continue: true
    - matchers:
      - severity="ticket"
      receiver: jira-network
      continue: true
    - receiver: slack-network
  - matchers:
    - team="data-platform"
    receiver: slack-data-platform
    routes:
    - matchers:
      - severity=~"page|critical"
      receiver: pagerduty-data-platform
      continue: true
    - matchers:
      - severity="ticket"
      receiver: jira-data-platform
      continue: true
    - receiver: slack-data-platform
  - matchers:
    - team="database-reliability"
    receiver: slack-database-reliability
    routes:
    - matchers:
      - severity=~"page|critical"
      receiver: pagerduty-database-reliability
      continue: true
    - matchers:
      - severity="ticket"
      receiver: jira-database-reliability
      continue: true
    - receiver: slack-database-reliability
  - matchers:
    - team="build-infra"
    receiver: slack-build-infra
    routes:
    - matchers:
      - severity=~"page|critical"
      receiver: pagerduty-build-infra
      continue: true
    - matchers:
      - severity="ticket"
      receiver: jira-build-infra
      continue: true
    - receiver: slack-build-infra
  - matchers:
    - team="edge"
    receiver: slack-edge
    routes:
    - matchers:
      - severity=~"page|critical"
      receiver: pagerduty-edge
      continue: true
    - matchers:
      - severity="ticket"
      receiver: jira-edge
      continue: true
    - receiver: slack-edge
  - matchers:
    - team="platform"
    receiver: slack-platform
    group_wait: 10s
    routes:
    - matchers:
      - severity=~"page|critical"
      receiver: pagerduty-platform
      continue: true
    - matchers:
      - severity="ticket"
      receiver: jira-platform
      continue: true
    # tickets and warnings per pod in Slack, so the channel shows which pod; pages group per service above
    - receiver: slack-platform
      group_by: [alertname, pod, service]
  - matchers:
    - team="messaging"
    receiver: slack-messaging
    routes:
    - matchers:
      - severity=~"page|critical"
      receiver: pagerduty-messaging
      continue: true
    - matchers:
      - severity="ticket"
      receiver: jira-messaging
      continue: true
    - receiver: slack-messaging
  # storage wanted tickets in Slack as well as Jira (SRE-2678)
  - matchers:
    - team="storage"
    receiver: slack-storage
    routes:
    - matchers:
      - severity=~"page|critical"
      receiver: pagerduty-storage
      continue: true
    - matchers:
      - severity="ticket"
      receiver: jira-storage
      continue: true
    - receiver: slack-storage
receivers:
- name: slack-alerts-default
  slack_configs:
  - channel: "#alerts-default"
    send_resolved: true
- name: slack-sre-fyi
  slack_configs:
  - channel: "#sre-fyi"
    send_resolved: false
- name: slack-prometheus-meta
  slack_configs:
  - channel: "#prometheus-meta"
- name: pagerduty-sre
  pagerduty_configs:
  - routing_key_file: /etc/alertmanager/secrets/pagerduty/sre
- name: pagerduty-build-infra
  pagerduty_configs:
  - routing_key_file: /etc/alertmanager/secrets/pagerduty/build-infra
- name: slack-build-infra
  slack_configs:
  - channel: "#build-infra-alerts"
    send_resolved: true
- name: jira-build-infra
  webhook_configs:
  - url: https://jira-bridge.prattbilling.example/hooks/build_infra
- name: pagerduty-claims
  pagerduty_configs:
  - routing_key_file: /etc/alertmanager/secrets/pagerduty/claims
- name: slack-claims
  slack_configs:
  - channel: "#claims-alerts"
    send_resolved: true
- name: jira-claims
  webhook_configs:
  - url: https://jira-bridge.prattbilling.example/hooks/claims
- name: pagerduty-clinical-ops
  pagerduty_configs:
  - routing_key_file: /etc/alertmanager/secrets/pagerduty/clinical-ops
- name: slack-clinical-ops
  slack_configs:
  - channel: "#clinical-ops-alerts"
    send_resolved: true
- name: jira-clinical-ops
  webhook_configs:
  - url: https://jira-bridge.prattbilling.example/hooks/clinical_ops
- name: pagerduty-data-platform
  pagerduty_configs:
  - routing_key_file: /etc/alertmanager/secrets/pagerduty/data-platform
- name: slack-data-platform
  slack_configs:
  - channel: "#data-platform-alerts"
    send_resolved: true
- name: jira-data-platform
  webhook_configs:
  - url: https://jira-bridge.prattbilling.example/hooks/data_platform
- name: pagerduty-database-reliability
  pagerduty_configs:
  - routing_key_file: /etc/alertmanager/secrets/pagerduty/database-reliability
- name: slack-database-reliability
  slack_configs:
  - channel: "#database-reliability-alerts"
    send_resolved: true
- name: jira-database-reliability
  webhook_configs:
  - url: https://jira-bridge.prattbilling.example/hooks/database_reliability
- name: pagerduty-edge
  pagerduty_configs:
  - routing_key_file: /etc/alertmanager/secrets/pagerduty/edge
- name: slack-edge
  slack_configs:
  - channel: "#edge-alerts"
    send_resolved: true
- name: jira-edge
  webhook_configs:
  - url: https://jira-bridge.prattbilling.example/hooks/edge
- name: pagerduty-eligibility
  pagerduty_configs:
  - routing_key_file: /etc/alertmanager/secrets/pagerduty/eligibility
- name: slack-eligibility
  slack_configs:
  - channel: "#eligibility-alerts"
    send_resolved: true
- name: jira-eligibility
  webhook_configs:
  - url: https://jira-bridge.prattbilling.example/hooks/eligibility
- name: pagerduty-member-experience
  pagerduty_configs:
  - routing_key_file: /etc/alertmanager/secrets/pagerduty/member-experience
- name: slack-member-experience
  slack_configs:
  - channel: "#member-experience-alerts"
    send_resolved: true
- name: jira-member-experience
  webhook_configs:
  - url: https://jira-bridge.prattbilling.example/hooks/member_experience
- name: pagerduty-messaging
  pagerduty_configs:
  - routing_key_file: /etc/alertmanager/secrets/pagerduty/messaging
- name: slack-messaging
  slack_configs:
  - channel: "#messaging-alerts"
    send_resolved: true
- name: jira-messaging
  webhook_configs:
  - url: https://jira-bridge.prattbilling.example/hooks/messaging
- name: pagerduty-network
  pagerduty_configs:
  - routing_key_file: /etc/alertmanager/secrets/pagerduty/network
- name: slack-network
  slack_configs:
  - channel: "#network-alerts"
    send_resolved: true
- name: jira-network
  webhook_configs:
  - url: https://jira-bridge.prattbilling.example/hooks/network
- name: pagerduty-payer-integrations
  pagerduty_configs:
  - routing_key_file: /etc/alertmanager/secrets/pagerduty/payer-integrations
- name: slack-payer-integrations
  slack_configs:
  - channel: "#payer-integrations-alerts"
    send_resolved: true
- name: jira-payer-integrations
  webhook_configs:
  - url: https://jira-bridge.prattbilling.example/hooks/payer_integrations
- name: pagerduty-platform
  pagerduty_configs:
  - routing_key_file: /etc/alertmanager/secrets/pagerduty/platform
- name: slack-platform
  slack_configs:
  - channel: "#platform-alerts"
    send_resolved: true
- name: jira-platform
  webhook_configs:
  - url: https://jira-bridge.prattbilling.example/hooks/platform
- name: pagerduty-provider-data
  pagerduty_configs:
  - routing_key_file: /etc/alertmanager/secrets/pagerduty/provider-data
- name: slack-provider-data
  slack_configs:
  - channel: "#provider-data-alerts"
    send_resolved: true
- name: jira-provider-data
  webhook_configs:
  - url: https://jira-bridge.prattbilling.example/hooks/provider_data
# routing key rotated in SRE-2674
- name: pagerduty-storage
  pagerduty_configs:
  - routing_key_file: /etc/alertmanager/secrets/pagerduty/storage
- name: slack-storage
  slack_configs:
  - channel: "#storage-alerts"
    send_resolved: true
- name: jira-storage
  webhook_configs:
  - url: https://jira-bridge.prattbilling.example/hooks/storage
# kept for the platform Prometheus until its config is cleaned up
- name: slack-ops-legacy
  slack_configs:
  - channel: "#ops-alerts-legacy"
    send_resolved: true
- name: slack-claims-oncall
  slack_configs:
  - channel: "#claims-oncall"
    send_resolved: true
inhibit_rules:
# a critical copy holds back the warning copy of the same alert
- source_matchers:
  - severity="critical"
  target_matchers:
  - severity="warning"
  equal: [alertname, service]
AF_EOF
mkdir -p 'rules'
cat > 'rules/clinical-ops-rules.yaml' <<'AF_EOF'
apiVersion: monitoring.coreos.com/v1
kind: PrometheusRule
metadata:
  name: clinical-ops-rules
  namespace: monitoring
  labels:
    role: alert-rules
spec:
  groups:
  - name: prior-auth-svc
    rules:
    - alert: PriorAuthSvcDown
      expr: |
        sum by (service) (up{service="prior-auth-svc"}) == 0
        or absent(up{service="prior-auth-svc"})
      for: 3m
      labels:
        severity: page
        team: clinical-ops
      annotations:
        summary: prior-auth-svc has no healthy scrape targets
        runbook_url: https://runbooks.prattbilling.example/alerts/PriorAuthSvcDown
    - alert: PriorAuthSvcHighErrorRatio
      expr: |
        sum by (service) (rate(http_requests_total{service="prior-auth-svc",code=~"5.."}[5m]))
        / sum by (service) (rate(http_requests_total{service="prior-auth-svc"}[5m])) > 0.1
      for: 10m
      labels:
        severity: page
        team: clinical-ops
      annotations:
        summary: "{{ $labels.service }} is failing {{ $value | humanizePercentage }} of requests"
        runbook_url: https://runbooks.prattbilling.example/alerts/PriorAuthSvcHighErrorRatio
    # factors from the SRE workbook's multiwindow table, don't tune per service
    - alert: PriorAuthSvcErrorBudgetBurnFast
      expr: |
        slo:sli_error:ratio_rate1h{service="prior-auth-svc"} > (14.4 * 0.001)
        and slo:sli_error:ratio_rate5m{service="prior-auth-svc"} > (14.4 * 0.001)
      for: 2m
      labels:
        severity: page
        team: clinical-ops
        slo: prior-auth-svc-availability
      annotations:
        summary: "{{ $labels.service }} is spending its error budget fast"
        runbook_url: https://runbooks.prattbilling.example/alerts/PriorAuthSvcErrorBudgetBurnFast
    - alert: PriorAuthSvcErrorBudgetBurnSlow
      expr: |
        slo:sli_error:ratio_rate6h{service="prior-auth-svc"} > (6 * 0.001)
        and slo:sli_error:ratio_rate30m{service="prior-auth-svc"} > (6 * 0.001)
      for: 15m
      labels:
        severity: ticket
        team: clinical-ops
        slo: prior-auth-svc-availability
      annotations:
        summary: "{{ $labels.service }} is spending its error budget steadily"
        runbook_url: https://runbooks.prattbilling.example/alerts/PriorAuthSvcErrorBudgetBurnSlow
  - name: fax-ingest
    rules:
    - alert: FaxIngestDown
      expr: |
        sum by (service) (up{service="fax-ingest"}) == 0
        or absent(up{service="fax-ingest"})
      for: 3m
      labels:
        severity: page
        team: clinical-ops
      annotations:
        summary: fax-ingest has no healthy scrape targets
        runbook_url: https://runbooks.prattbilling.example/alerts/FaxIngestDown
    # 5% from SRE-1187; callers retry fax-ingest, a few errors never reach a user
    - alert: FaxIngestHighErrorRatio
      expr: |
        sum by (service) (rate(http_requests_total{service="fax-ingest",code=~"5.."}[5m]))
        / sum by (service) (rate(http_requests_total{service="fax-ingest"}[5m])) > 0.05
      for: 10m
      labels:
        severity: page
        team: clinical-ops
      annotations:
        summary: "{{ $labels.service }} is failing {{ $value | humanizePercentage }} of requests"
        runbook_url: https://runbooks.prattbilling.example/alerts/FaxIngestHighErrorRatio
    # average the pods: they all run with the same limit, so the mean is what we size it by
    - alert: FaxIngestCpuThrottled
      expr: |
        avg by (service) (rate(container_cpu_cfs_throttled_periods_total{service="fax-ingest",container="fax-ingest"}[5m]) / rate(container_cpu_cfs_periods_total{service="fax-ingest",container="fax-ingest"}[5m])) > 0.25
      for: 30m
      labels:
        severity: ticket
        team: clinical-ops
      annotations:
        summary: "{{ $labels.service }} pods spend over a quarter of their CPU periods throttled"
        runbook_url: https://runbooks.prattbilling.example/alerts/FaxIngestCpuThrottled
  - name: prior-worker
    rules:
    - alert: PriorWorkerDown
      expr: |
        sum by (service) (up{service="prior-worker"}) == 0
        or absent(up{service="prior-worker"})
      for: 3m
      labels:
        severity: page
        team: clinical-ops
      annotations:
        summary: prior-worker has no healthy scrape targets
        runbook_url: https://runbooks.prattbilling.example/alerts/PriorWorkerDown
    - alert: PriorWorkerHighErrorRatio
      expr: |
        sum by (service) (rate(http_requests_total{service="prior-worker",code=~"5.."}[5m]))
        / sum by (service) (rate(http_requests_total{service="prior-worker"}[5m])) > 0.1
      for: 10m
      labels:
        severity: page
        team: clinical-ops
      annotations:
        summary: "{{ $labels.service }} is failing {{ $value | humanizePercentage }} of requests"
        runbook_url: https://runbooks.prattbilling.example/alerts/PriorWorkerHighErrorRatio
    # average over the targets: half of them gone is a ticket even while the rest carry the load
    - alert: PriorWorkerTargetsHalfDown
      expr: |
        avg by (service) (up{service="prior-worker"}) < 0.5
        and on (service) count by (service) (up{service="prior-worker"}) >= 2
      for: 10m
      labels:
        severity: ticket
        team: clinical-ops
      annotations:
        summary: "{{ $labels.service }} has lost half of its targets"
        runbook_url: https://runbooks.prattbilling.example/alerts/PriorWorkerTargetsHalfDown
AF_EOF
mkdir -p 'rules'
cat > 'rules/disk.yml' <<'AF_EOF'
# host disks (infra)
groups:
- name: disk
  rules:
  - alert: HostDiskAlmostFull
    expr: node_filesystem_avail_bytes{fstype!~"tmpfs|overlay"} / node_filesystem_size_bytes < 0.1
    for: "5m"
    labels: {severity: warning, team: infra}
    annotations:
      summary: "{{ $labels.instance }} {{ $labels.mountpoint }} is under 10% free"
      runbook_url: https://runbooks.prattbilling.example/alerts/HostDiskAlmostFull
AF_EOF
mkdir -p 'rules'
cat > 'rules/legacy-provider-data.yml' <<'AF_EOF'
# provider-data alerts from before the conventions in README.md.
# Don't reformat in passing; move things out when you touch them for a reason.
groups:
# old dashboard records; the svc-overview board still reads these
- name: provider-data-records
  rules:
  - record: job:http_requests:rate5m
    expr: sum by (job, service) (rate(http_requests_total{service="provider-dir"}[5m]))
  - record: job:http_errors:rate5m
    expr: sum by (job, service) (rate(http_requests_total{service="provider-dir",code=~"5.."}[5m]))
- name: provider-dir
  rules:
  # threshold agreed with provider-data in SRE-1634
  - alert: ProviderDirHighErrorRatio
    expr: sum by (service) (rate(http_requests_total{service="provider-dir",code=~"5.."}[5m])) / sum by (service) (rate(http_requests_total{service="provider-dir"}[5m])) > 0.05
    for: "10m"
    labels: {severity: page, team: provider-data}
    annotations:
      summary: "{{ $labels.service }} is failing {{ $value | humanizePercentage }} of requests"
      runbook_url: https://runbooks.prattbilling.example/alerts/ProviderDirHighErrorRatio
  - alert: ProviderDirLatencyHigh
    expr: histogram_quantile(0.99, sum by (service, le) (rate(http_request_duration_seconds_bucket{service="provider-dir"}[5m]))) > 0.5
    for: "10m"
    labels: {severity: warning, team: provider-data}
    annotations:
      summary: "{{ $labels.service }} p99 above 500ms"
      runbook_url: https://runbooks.prattbilling.example/alerts/ProviderDirLatencyHigh
  - alert: ProviderDirLatencyHigh
    expr: histogram_quantile(0.99, sum by (service, le) (rate(http_request_duration_seconds_bucket{service="provider-dir"}[5m]))) > 1
    for: "10m"
    labels: {severity: critical, team: provider-data}
    annotations:
      summary: "{{ $labels.service }} p99 above 1s"
      runbook_url: https://runbooks.prattbilling.example/alerts/ProviderDirLatencyHigh
  # max, not avg: one pod with a full pool already queues requests
  - alert: ProviderDirDbConnectionsHigh
    expr: max by (service) (db_pool_connections_active{service="provider-dir"} / db_pool_connections_max{service="provider-dir"}) > 0.8
    for: "5m"
    labels: {severity: warning, team: provider-data}
    annotations:
      summary: "{{ $labels.service }} is using over 80% of its DB pool"
      runbook_url: https://runbooks.prattbilling.example/alerts/ProviderDirDbConnectionsHigh
  - alert: ProviderDirDbConnectionsHigh
    expr: max by (service) (db_pool_connections_active{service="provider-dir"} / db_pool_connections_max{service="provider-dir"}) > 0.95
    for: "5m"
    labels: {severity: critical, team: provider-data}
    annotations:
      summary: "{{ $labels.service }} DB pool nearly exhausted"
      runbook_url: https://runbooks.prattbilling.example/alerts/ProviderDirDbConnectionsHigh
AF_EOF
mkdir -p 'rules'
cat > 'rules/member-experience-rules.yaml' <<'AF_EOF'
apiVersion: monitoring.coreos.com/v1
kind: PrometheusRule
metadata:
  name: member-experience-rules
  namespace: monitoring
  labels:
    role: alert-rules
spec:
  groups:
  - name: member-api
    rules:
    - alert: MemberApiDown
      expr: |
        sum by (service) (up{service="member-api"}) == 0
        or absent(up{service="member-api"})
      for: 3m
      labels:
        severity: page
        team: member-experience
      annotations:
        summary: member-api has no healthy scrape targets
        runbook_url: https://runbooks.prattbilling.example/alerts/MemberApiDown
    - alert: MemberApiHighErrorRatio
      expr: |
        sum by (service) (rate(http_requests_total{service="member-api",code=~"5.."}[5m]))
        / sum by (service) (rate(http_requests_total{service="member-api"}[5m])) > 0.05
      for: 10m
      labels:
        severity: page
        team: member-experience
      annotations:
        summary: "{{ $labels.service }} is failing {{ $value | humanizePercentage }} of requests"
        runbook_url: https://runbooks.prattbilling.example/alerts/MemberApiHighErrorRatio
    - alert: MemberApiTrafficBelowFloor
      expr: |
        sum by (service) (rate(http_requests_total{service="member-api"}[5m])) < 6
        and on (service) sum by (service) (up{service="member-api"}) > 0
      for: 5m
      labels:
        severity: page
        team: member-experience
      annotations:
        summary: "{{ $labels.service }} is serving under its traffic floor with its pods up"
        runbook_url: https://runbooks.prattbilling.example/alerts/MemberApiTrafficBelowFloor
    - alert: MemberApiErrorBudgetBurnFast
      expr: |
        slo:sli_error:ratio_rate1h{service="member-api"} > (14.4 * 0.001)
        and slo:sli_error:ratio_rate5m{service="member-api"} > (14.4 * 0.001)
      for: 2m
      labels:
        severity: page
        team: member-experience
        slo: member-api-availability
      annotations:
        summary: "{{ $labels.service }} is spending its error budget fast"
        runbook_url: https://runbooks.prattbilling.example/alerts/MemberApiErrorBudgetBurnFast
    - alert: MemberApiErrorBudgetBurnSlow
      expr: |
        slo:sli_error:ratio_rate6h{service="member-api"} > (6 * 0.001)
        and slo:sli_error:ratio_rate30m{service="member-api"} > (6 * 0.001)
      for: 15m
      labels:
        severity: ticket
        team: member-experience
        slo: member-api-availability
      annotations:
        summary: "{{ $labels.service }} is spending its error budget steadily"
        runbook_url: https://runbooks.prattbilling.example/alerts/MemberApiErrorBudgetBurnSlow
  - name: eligibility-svc
    rules:
    - alert: EligibilitySvcDown
      expr: |
        sum by (service) (up{service="eligibility-svc"}) == 0
        or absent(up{service="eligibility-svc"})
      for: 3m
      labels:
        severity: page
        team: eligibility
      annotations:
        summary: eligibility-svc has no healthy scrape targets
        runbook_url: https://runbooks.prattbilling.example/alerts/EligibilitySvcDown
    - alert: EligibilitySvcHighErrorRatio
      expr: |
        sum by (service) (rate(grpc_server_handled_total{service="eligibility-svc",grpc_code=~"Unavailable|Internal|DeadlineExceeded|Unknown|DataLoss"}[5m]))
        / sum by (service) (rate(grpc_server_handled_total{service="eligibility-svc"}[5m])) > 0.1
      for: 10m
      labels:
        severity: page
        team: eligibility
      annotations:
        summary: "{{ $labels.service }} is failing {{ $value | humanizePercentage }} of requests"
        runbook_url: https://runbooks.prattbilling.example/alerts/EligibilitySvcHighErrorRatio
    - alert: EligibilitySvcErrorBudgetBurnFast
      expr: |
        slo:sli_error:ratio_rate1h{service="eligibility-svc"} > (14.4 * 0.005)
        and slo:sli_error:ratio_rate5m{service="eligibility-svc"} > (14.4 * 0.005)
      for: 2m
      labels:
        severity: page
        team: eligibility
        slo: eligibility-svc-availability
      annotations:
        summary: "{{ $labels.service }} is spending its error budget fast"
        runbook_url: https://runbooks.prattbilling.example/alerts/EligibilitySvcErrorBudgetBurnFast
    - alert: EligibilitySvcErrorBudgetBurnSlow
      expr: |
        slo:sli_error:ratio_rate6h{service="eligibility-svc"} > (6 * 0.005)
        and slo:sli_error:ratio_rate30m{service="eligibility-svc"} > (6 * 0.005)
      for: 15m
      labels:
        severity: ticket
        team: eligibility
        slo: eligibility-svc-availability
      annotations:
        summary: "{{ $labels.service }} is spending its error budget steadily"
        runbook_url: https://runbooks.prattbilling.example/alerts/EligibilitySvcErrorBudgetBurnSlow
AF_EOF
mkdir -p 'rules'
cat > 'rules/slo-provider-dir.yml' <<'AF_EOF'
groups:
- name: slo-provider-dir
  rules:
  - alert: ProviderDirErrorBudgetBurnFast
    expr: |
      slo:sli_error:ratio_rate1h{service="provider-dir"} > (3.36 * 0.01)
      and slo:sli_error:ratio_rate5m{service="provider-dir"} > (3.36 * 0.01)
    for: 2m
    labels:
      severity: page
      team: provider-data
      slo: provider-dir-availability
    annotations:
      summary: "{{ $labels.service }} is spending its error budget fast"
      runbook_url: https://runbooks.prattbilling.example/alerts/ProviderDirErrorBudgetBurnFast
  - alert: ProviderDirErrorBudgetBurnSlow
    expr: |
      slo:sli_error:ratio_rate6h{service="provider-dir"} > (1.4 * 0.01)
      and slo:sli_error:ratio_rate30m{service="provider-dir"} > (1.4 * 0.01)
    for: 15m
    labels:
      severity: ticket
      team: provider-data
      slo: provider-dir-availability
    annotations:
      summary: "{{ $labels.service }} is spending its error budget steadily"
      runbook_url: https://runbooks.prattbilling.example/alerts/ProviderDirErrorBudgetBurnSlow
AF_EOF