tasks/afx-e2-s02/solution/solve.sh

#!/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="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="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
  - 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
    # tickets and warnings per pod in Slack, so the channel shows which pod; pages group per service above
    - receiver: slack-member-experience
      group_by: [alertname, pod, service]
  - 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
  # 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
  # teams below route alerts from the platform and data Prometheus servers
  - 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
  # messaging wanted tickets in Slack as well as Jira (OPS-1188)
  - 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
  - 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="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="data-platform"
    receiver: slack-data-platform
    group_wait: 10s
    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="security-ops"
    receiver: slack-security-ops
    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="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="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
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.linneavard.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.linneavard.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.linneavard.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.linneavard.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.linneavard.example/hooks/database_reliability
- 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.linneavard.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.linneavard.example/hooks/messaging
- 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.linneavard.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.linneavard.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.linneavard.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.linneavard.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.linneavard.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.linneavard.example/hooks/security_ops
# nothing routes here since the rota moved to PagerDuty; ask before deleting
- name: slack-old-oncall
  slack_configs:
  - channel: "#oncall-old"
    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]
- source_matchers:
  - alertname="ProviderDirDown"
  target_matchers:
  - alertname=~"ProviderDirErrorBudgetBurnFast|ProviderDirErrorBudgetBurnSlow|ProviderDirHighErrorRatio"
  equal: [service]
AF_EOF
mkdir -p 'rules'
cat > 'rules/claims-rules.yaml' <<'AF_EOF'
apiVersion: monitoring.coreos.com/v1
kind: PrometheusRule
metadata:
  name: claims-rules
  namespace: monitoring
  labels:
    role: alert-rules
spec:
  groups:
  - name: claims-api
    rules:
    - 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.linneavard.example/alerts/ClaimsApiDown
    - 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.linneavard.example/alerts/ClaimsApiHighErrorRatio
    - alert: ClaimsApiErrorBudgetBurnFast
      expr: |
        slo:sli_error:ratio_rate1h{service="claims-api"} > (14.4 * 0.005)
        and slo:sli_error:ratio_rate5m{service="claims-api"} > (14.4 * 0.005)
      for: 2m
      labels:
        severity: page
        team: claims
        slo: claims-api-availability
      annotations:
        summary: "{{ $labels.service }} is spending its error budget fast"
        runbook_url: https://runbooks.linneavard.example/alerts/ClaimsApiErrorBudgetBurnFast
    - alert: ClaimsApiErrorBudgetBurnSlow
      expr: |
        slo:sli_error:ratio_rate6h{service="claims-api"} > (6 * 0.005)
        and slo:sli_error:ratio_rate30m{service="claims-api"} > (6 * 0.005)
      for: 15m
      labels:
        severity: ticket
        team: claims
        slo: claims-api-availability
      annotations:
        summary: "{{ $labels.service }} is spending its error budget steadily"
        runbook_url: https://runbooks.linneavard.example/alerts/ClaimsApiErrorBudgetBurnSlow
    - 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.linneavard.example/alerts/DbClientConnectionErrors
  - name: adjudication-worker
    rules:
    - 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.linneavard.example/alerts/AdjudicationWorkerDown
    - 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.linneavard.example/alerts/AdjudicationWorkerHighErrorRatio
    - 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.linneavard.example/alerts/DbClientConnectionErrors
  - name: claims-indexer
    rules:
    - 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.linneavard.example/alerts/ClaimsIndexerDown
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.linneavard.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]))
  # running total for the 'errors since deploy' stat on svc-overview
  - record: service:http_errors:sum
    expr: sum by (service) (http_requests_total{code=~"5.."})
- name: provider-dir
  rules:
  # threshold agreed with provider-data in OPS-1330
  - 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.1
    for: "10m"
    labels: {severity: page, team: provider-data}
    annotations:
      summary: "{{ $labels.service }} is failing {{ $value | humanizePercentage }} of requests"
      runbook_url: https://runbooks.linneavard.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.linneavard.example/alerts/ProviderDirLatencyHigh
  # TODO(2024) move to a latency SLO once we have one
  - 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.linneavard.example/alerts/ProviderDirLatencyHigh
  - 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.linneavard.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.linneavard.example/alerts/ProviderDirDbConnectionsHigh
  - alert: ProviderDirErrorBurst
    expr: sum by (service) (rate(http_requests_total{service="provider-dir",code=~"5.."}[5m])) > 4
    for: "10m"
    labels: {severity: page, team: provider-data}
    annotations:
      summary: "{{ $labels.service }} is returning more than 4 errors/s"
      runbook_url: https://runbooks.linneavard.example/alerts/ProviderDirErrorBurst
AF_EOF