partial/afx-e2-s03/solve.sh

#!/bin/bash
# partial: even-indexed requirements + one plausible mistake
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
  # claims: still on the old match syntax
  - match:
      team: claims
    receiver: slack-claims
    routes:
    - match_re:
        severity: page|critical
      receiver: pagerduty-claims
      continue: true
    - match:
        severity: ticket
      receiver: jira-claims
      continue: true
    - receiver: slack-claims
  - 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
  - matchers:
    - team="provider-data"
    receiver: slack-provider-data
    routes:
    - matchers:
      - severity=~"page|critical"
      receiver: pagerduty-provider-data
      continue: true
    - matchers:
      - severity="ticket"
      receiver: jira-provider-data
      continue: true
    - receiver: slack-provider-data
  # teams below route alerts from the platform and data Prometheus servers
  - 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="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
  # edge wanted tickets in Slack as well as Jira (SRE-2624)
  - matchers:
    - team="edge"
    receiver: slack-edge
    routes:
    - matchers:
      - severity=~"page|critical"
      receiver: pagerduty-edge
      continue: true
    - matchers:
      - severity="ticket"
      receiver: jira-edge
      continue: true
    # tickets and warnings per pod in Slack, so the channel shows which pod; pages group per service above
    - receiver: slack-edge
      group_by: [alertname, pod, service]
  # security-ops asked for hourly repeats while something is still firing
  - matchers:
    - team="security-ops"
    receiver: slack-security-ops
    repeat_interval: 1h
    routes:
    - matchers:
      - severity=~"page|critical"
      receiver: pagerduty-security-ops
      continue: true
    - matchers:
      - severity="ticket"
      receiver: jira-security-ops
      continue: true
    - receiver: slack-security-ops
  - matchers:
    - team="platform"
    receiver: slack-platform
    routes:
    - matchers:
      - severity=~"page|critical"
      receiver: pagerduty-platform
      continue: true
    - matchers:
      - severity="ticket"
      receiver: jira-platform
      continue: true
    - receiver: slack-platform
  - matchers:
    - team="ml-platform"
    receiver: slack-ml-platform
    routes:
    - matchers:
      - severity=~"page|critical"
      receiver: pagerduty-ml-platform
      continue: true
    - matchers:
      - severity="ticket"
      receiver: jira-ml-platform
      continue: true
    - receiver: slack-ml-platform
  - matchers:
    - team="network"
    receiver: slack-network
    routes:
    - matchers:
      - severity=~"page|critical"
      receiver: pagerduty-network
      continue: true
    - matchers:
      - severity="ticket"
      receiver: jira-network
      continue: true
    - receiver: slack-network
  - 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
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
# routing key rotated in SRE-1830
- 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.nidaan.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.nidaan.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.nidaan.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.nidaan.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.nidaan.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.nidaan.example/hooks/edge
- 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.nidaan.example/hooks/member_experience
- name: pagerduty-ml-platform
  pagerduty_configs:
  - routing_key_file: /etc/alertmanager/secrets/pagerduty/ml-platform
- name: slack-ml-platform
  slack_configs:
  - channel: "#ml-platform-alerts"
    send_resolved: true
- name: jira-ml-platform
  webhook_configs:
  - url: https://jira-bridge.nidaan.example/hooks/ml_platform
- 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.nidaan.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.nidaan.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.nidaan.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.nidaan.example/hooks/provider_data
- name: pagerduty-security-ops
  pagerduty_configs:
  - routing_key_file: /etc/alertmanager/secrets/pagerduty/security-ops
- name: slack-security-ops
  slack_configs:
  - channel: "#security-ops-alerts"
    send_resolved: true
- name: jira-security-ops
  webhook_configs:
  - url: https://jira-bridge.nidaan.example/hooks/security_ops
# kept for the platform Prometheus until its config is cleaned up
- name: slack-ops-legacy
  slack_configs:
  - channel: "#ops-alerts-legacy"
    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/capacity.yml' <<'AF_EOF'
# Capacity tickets. Pages for crashes come from the platform Prometheus.
groups:
- name: capacity
  rules:
  - alert: ContainerMemoryNearLimit
    expr: |
      max by (service) (container_memory_working_set_bytes{service="fax-ingest",container="fax-ingest"} / container_spec_memory_limit_bytes{service="fax-ingest",container="fax-ingest"}) > 0.9
    for: 15m
    labels:
      severity: ticket
      team: clinical-ops
    annotations:
      summary: "{{ $labels.service }} keeps running close to its memory limit"
      runbook_url: https://runbooks.nidaan.example/alerts/ContainerMemoryNearLimit
AF_EOF
mkdir -p 'rules'
cat > 'rules/legacy-claims.yml' <<'AF_EOF'
# claims 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: claims-records
  rules:
  - record: job:http_requests:rate5m
    expr: sum by (job, service) (rate(http_requests_total{service=~"claims-api|adjudication-worker"}[5m]))
  - record: job:http_errors:rate5m
    expr: sum by (job, service) (rate(http_requests_total{service=~"claims-api|adjudication-worker",code=~"5.."}[5m]))
- name: claims-api
  rules:
  # threshold agreed with claims in SRE-1825
  - alert: ClaimsApiHighErrorRatio
    expr: sum by (service) (rate(http_requests_total{service="claims-api",code=~"5.."}[5m])) / sum by (service) (rate(http_requests_total{service="claims-api"}[5m])) > 0.1
    for: "10m"
    labels: {severity: page, team: claims}
    annotations:
      summary: "{{ $labels.service }} is failing {{ $value | humanizePercentage }} of requests"
      runbook_url: https://runbooks.nidaan.example/alerts/ClaimsApiHighErrorRatio
  - alert: ClaimsApiLatencyHigh
    expr: histogram_quantile(0.99, sum by (service, le) (rate(http_request_duration_seconds_bucket{service="claims-api"}[5m]))) > 0.5
    for: "10m"
    labels: {severity: warning, team: claims}
    annotations:
      summary: "{{ $labels.service }} p99 above 500ms"
      runbook_url: https://runbooks.nidaan.example/alerts/ClaimsApiLatencyHigh
  - alert: ClaimsApiLatencyHigh
    expr: histogram_quantile(0.99, sum by (service, le) (rate(http_request_duration_seconds_bucket{service="claims-api"}[5m]))) > 1
    for: "10m"
    labels: {severity: critical, team: claims}
    annotations:
      summary: "{{ $labels.service }} p99 above 1s"
      runbook_url: https://runbooks.nidaan.example/alerts/ClaimsApiLatencyHigh
  - alert: ClaimsApiDbConnectionsHigh
    expr: max by (service) (db_pool_connections_active{service="claims-api"} / db_pool_connections_max{service="claims-api"}) > 0.8
    for: "5m"
    labels: {severity: warning, team: claims}
    annotations:
      summary: "{{ $labels.service }} is using over 80% of its DB pool"
      runbook_url: https://runbooks.nidaan.example/alerts/ClaimsApiDbConnectionsHigh
  - alert: ClaimsApiDbConnectionsHigh
    expr: max by (service) (db_pool_connections_active{service="claims-api"} / db_pool_connections_max{service="claims-api"}) > 0.95
    for: "5m"
    labels: {severity: critical, team: claims}
    annotations:
      summary: "{{ $labels.service }} DB pool nearly exhausted"
      runbook_url: https://runbooks.nidaan.example/alerts/ClaimsApiDbConnectionsHigh
  - alert: DbClientConnectionErrors
    expr: rate(db_client_connection_errors_total{service="claims-api"}[2m]) > 0.5
    for: "2m"
    labels: {severity: page, team: claims}
    annotations:
      summary: "{{ $labels.pod }} can't get database connections"
      runbook_url: https://runbooks.nidaan.example/alerts/DbClientConnectionErrors
  # average over the targets: half of them gone is a ticket even while the rest carry the load
  - alert: ClaimsApiTargetsHalfDown
    expr: avg by (service) (up{service="claims-api"}) < 0.5 and on (service) count by (service) (up{service="claims-api"}) >= 2
    for: "10m"
    labels: {severity: ticket, team: claims}
    annotations:
      summary: "{{ $labels.service }} has lost half of its targets"
      runbook_url: https://runbooks.nidaan.example/alerts/ClaimsApiTargetsHalfDown
  - alert: ClaimsApiDbConnectionsHigh
    expr: max by (service) (db_pool_connections_active{service="claims-api"} / db_pool_connections_max{service="claims-api"}) > 0.8
    for: "5m"
    labels: {severity: warning, team: claims}
    annotations:
      summary: "{{ $labels.service }} is using over 80% of its DB pool"
      runbook_url: https://wiki.nidaan.example/display/SRE/ClaimsApiDbConnectionsHigh+runbook
  - alert: ClaimsApiDbConnectionsHigh
    expr: max by (service) (db_pool_connections_active{service="claims-api"} / db_pool_connections_max{service="claims-api"}) > 0.95
    for: "5m"
    labels: {severity: critical, team: claims}
    annotations:
      summary: "{{ $labels.service }} DB pool nearly exhausted"
      runbook_url: https://wiki.nidaan.example/display/SRE/ClaimsApiDbConnectionsHigh+runbook
- name: adjudication-worker
  rules:
  # 2% from SRE-1150; callers retry adjudication-worker, a few errors never reach a user
  - alert: AdjudicationWorkerHighErrorRatio
    expr: sum by (service) (rate(http_requests_total{service="adjudication-worker",code=~"5.."}[5m])) / sum by (service) (rate(http_requests_total{service="adjudication-worker"}[5m])) > 0.02
    for: "10m"
    labels: {severity: page, team: claims}
    annotations:
      summary: "{{ $labels.service }} is failing {{ $value | humanizePercentage }} of requests"
      runbook_url: https://runbooks.nidaan.example/alerts/AdjudicationWorkerHighErrorRatio
  - alert: AdjudicationWorkerLatencyHigh
    expr: histogram_quantile(0.99, sum by (service, le) (rate(http_request_duration_seconds_bucket{service="adjudication-worker"}[5m]))) > 0.5
    for: "10m"
    labels: {severity: warning, team: claims}
    annotations:
      summary: "{{ $labels.service }} p99 above 500ms"
      runbook_url: https://runbooks.nidaan.example/alerts/AdjudicationWorkerLatencyHigh
  # TODO(2024) move to a latency SLO once we have one
  - alert: AdjudicationWorkerLatencyHigh
    expr: histogram_quantile(0.99, sum by (service, le) (rate(http_request_duration_seconds_bucket{service="adjudication-worker"}[5m]))) > 1
    for: "10m"
    labels: {severity: critical, team: claims}
    annotations:
      summary: "{{ $labels.service }} p99 above 1s"
      runbook_url: https://runbooks.nidaan.example/alerts/AdjudicationWorkerLatencyHigh
  - alert: DbClientConnectionErrors
    expr: rate(db_client_connection_errors_total{service="adjudication-worker"}[2m]) > 0.5
    for: "2m"
    labels: {severity: page, team: claims}
    annotations:
      summary: "{{ $labels.pod }} can't get database connections"
      runbook_url: https://runbooks.nidaan.example/alerts/DbClientConnectionErrors
  - alert: AdjudicationWorkerQueueBacklogHigh
    expr: max by (service) (work_queue_depth{service="adjudication-worker"}) > 5000
    for: "15m"
    labels: {severity: page, team: claims}
    annotations:
      summary: "{{ $labels.service }} has more than 5000 jobs waiting"
      runbook_url: https://runbooks.nidaan.example/alerts/AdjudicationWorkerQueueBacklogHigh
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=~"prior-auth-svc|provider-dir|fax-ingest"}[5m]))
  # keep: finance reads this one for the monthly availability report
  - record: job:http_errors:rate5m
    expr: sum by (job, service) (rate(http_requests_total{service=~"prior-auth-svc|provider-dir|fax-ingest",code=~"5.."}[5m]))
- name: prior-auth-svc
  rules:
  # threshold agreed with provider-data in SRE-1461
  - 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.05
    for: "10m"
    labels: {severity: page, team: clinical-ops}
    annotations:
      summary: "{{ $labels.service }} is failing {{ $value | humanizePercentage }} of requests"
      runbook_url: https://runbooks.nidaan.example/alerts/PriorAuthSvcHighErrorRatio
  - alert: PriorAuthSvcLatencyHigh
    expr: histogram_quantile(0.99, sum by (service, le) (rate(http_request_duration_seconds_bucket{service="prior-auth-svc"}[5m]))) > 0.5
    for: "10m"
    labels: {severity: warning, team: clinical-ops}
    annotations:
      summary: "{{ $labels.service }} p99 above 500ms"
      runbook_url: https://runbooks.nidaan.example/alerts/PriorAuthSvcLatencyHigh
  # TODO(2024) move to a latency SLO once we have one
  - alert: PriorAuthSvcLatencyHigh
    expr: histogram_quantile(0.99, sum by (service, le) (rate(http_request_duration_seconds_bucket{service="prior-auth-svc"}[5m]))) > 1
    for: "10m"
    labels: {severity: critical, team: clinical-ops}
    annotations:
      summary: "{{ $labels.service }} p99 above 1s"
      runbook_url: https://runbooks.nidaan.example/alerts/PriorAuthSvcLatencyHigh
- name: provider-dir
  rules:
  # 5% from SRE-2476; callers retry provider-dir, a few errors never reach a user
  - 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.nidaan.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.nidaan.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.nidaan.example/alerts/ProviderDirLatencyHigh
- name: fax-ingest
  rules:
  - 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.02
    for: "10m"
    labels: {severity: page, team: clinical-ops}
    annotations:
      summary: "{{ $labels.service }} is failing {{ $value | humanizePercentage }} of requests"
      runbook_url: https://runbooks.nidaan.example/alerts/FaxIngestHighErrorRatio
  - alert: FaxIngestLatencyHigh
    expr: histogram_quantile(0.99, sum by (service, le) (rate(http_request_duration_seconds_bucket{service="fax-ingest"}[5m]))) > 0.5
    for: "10m"
    labels: {severity: warning, team: clinical-ops}
    annotations:
      summary: "{{ $labels.service }} p99 above 500ms"
      runbook_url: https://runbooks.nidaan.example/alerts/FaxIngestLatencyHigh
  - alert: FaxIngestLatencyHigh
    expr: histogram_quantile(0.99, sum by (service, le) (rate(http_request_duration_seconds_bucket{service="fax-ingest"}[5m]))) > 1
    for: "10m"
    labels: {severity: critical, team: clinical-ops}
    annotations:
      summary: "{{ $labels.service }} p99 above 1s"
      runbook_url: https://runbooks.nidaan.example/alerts/FaxIngestLatencyHigh
  - alert: FaxIngestDbConnectionsHigh
    expr: max by (service) (db_pool_connections_active{service="fax-ingest"} / db_pool_connections_max{service="fax-ingest"}) > 0.8
    for: "5m"
    labels: {severity: warning, team: clinical-ops}
    annotations:
      summary: "{{ $labels.service }} is using over 80% of its DB pool"
      runbook_url: https://runbooks.nidaan.example/alerts/FaxIngestDbConnectionsHigh
  - alert: FaxIngestDbConnectionsHigh
    expr: max by (service) (db_pool_connections_active{service="fax-ingest"} / db_pool_connections_max{service="fax-ingest"}) > 0.95
    for: "5m"
    labels: {severity: critical, team: clinical-ops}
    annotations:
      summary: "{{ $labels.service }} DB pool nearly exhausted"
      runbook_url: https://runbooks.nidaan.example/alerts/FaxIngestDbConnectionsHigh
AF_EOF
mkdir -p 'rules'
cat > 'rules/service-health.yml' <<'AF_EOF'
# One Down alert per service. See README, Service health.
groups:
- name: service-health
  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.nidaan.example/alerts/PriorAuthSvcDown
  # for: 3m so a rolling restart doesn't page; claims-api cycles one pod at a time
  - alert: ClaimsApiDown
    expr: |
      sum by (service) (up{service="claims-api"}) == 0
      or absent(up{service="claims-api"})
    for: 3m
    labels:
      severity: page
      team: claims
    annotations:
      summary: claims-api has no healthy scrape targets
      runbook_url: https://runbooks.nidaan.example/alerts/ClaimsApiDown
  - alert: ProviderDirDown
    expr: |
      sum by (service) (up{service="provider-dir"}) == 0
      or absent(up{service="provider-dir"})
    for: 3m
    labels:
      severity: page
      team: provider-data
    annotations:
      summary: provider-dir has no healthy scrape targets
      runbook_url: https://runbooks.nidaan.example/alerts/ProviderDirDown
  - alert: AdjudicationWorkerDown
    expr: |
      sum by (service) (up{service="adjudication-worker"}) == 0
      or absent(up{service="adjudication-worker"})
    for: 3m
    labels:
      severity: page
      team: claims
    annotations:
      summary: adjudication-worker has no healthy scrape targets
      runbook_url: https://runbooks.nidaan.example/alerts/AdjudicationWorkerDown
  - alert: RemitExportDown
    expr: |
      sum by (service) (up{service="remit-export"}) == 0
      or absent(up{service="remit-export"})
    for: 3m
    labels:
      severity: page
      team: payer-integrations
    annotations:
      summary: remit-export has no healthy scrape targets
      runbook_url: https://runbooks.nidaan.example/alerts/RemitExportDown
  - 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.nidaan.example/alerts/FaxIngestDown
  - alert: ClaimsIndexerDown
    expr: |
      sum by (service) (up{service="claims-indexer"}) == 0
      or absent(up{service="claims-indexer"})
    for: 3m
    labels:
      severity: page
      team: claims
    annotations:
      summary: claims-indexer has no healthy scrape targets
      runbook_url: https://runbooks.nidaan.example/alerts/ClaimsIndexerDown
  # for: 3m so a rolling restart doesn't page; eligibility-svc cycles one pod at a time
  - alert: EligibilitySvcDown
    expr: |
      sum by (service) (up{service="eligibility-svc"}) == 0
      or absent(up{service="eligibility-svc"})
    for: 3m
    labels:
      severity: page
      team: payer-integrations
    annotations:
      summary: eligibility-svc has no healthy scrape targets
      runbook_url: https://runbooks.nidaan.example/alerts/EligibilitySvcDown
AF_EOF
mkdir -p 'rules'
cat > 'rules/slo-prior-auth-svc.yml' <<'AF_EOF'
groups:
- name: slo-prior-auth-svc
  rules:
  - 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.nidaan.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.nidaan.example/alerts/PriorAuthSvcErrorBudgetBurnSlow
AF_EOF