#!/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
  smtp_smarthost: smtp.halde.example:587
  smtp_from: alertmanager@halde.example
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:
    - alertname="ClusterUnreachable"
    receiver: pagerduty-platform
  # fulfillment: still on the old match syntax
  - match:
      team: fulfillment
    receiver: slack-fulfillment
    routes:
    - match_re:
        severity: page|critical
      receiver: pagerduty-fulfillment
      continue: true
    - match:
        severity: ticket
      receiver: jira-fulfillment
      continue: true
    - receiver: slack-fulfillment
  - matchers:
    - team="storefront"
    receiver: slack-storefront
    routes:
    - matchers:
      - severity=~"page|critical"
      receiver: pagerduty-storefront
      continue: true
    - matchers:
      - severity="ticket"
      receiver: jira-storefront
      continue: true
    - receiver: slack-storefront
  - matchers:
    - team="checkout-core"
    receiver: slack-checkout-core
    routes:
    - matchers:
      - severity=~"page|critical"
      receiver: pagerduty-checkout-core
      continue: true
    - matchers:
      - severity="ticket"
      receiver: jira-checkout-core
      continue: true
    - receiver: slack-checkout-core
  - matchers:
    - team="growth"
    receiver: slack-growth
    routes:
    - matchers:
      - severity=~"page|critical"
      receiver: pagerduty-growth
      continue: true
    - matchers:
      - severity="ticket"
      receiver: jira-growth
      continue: true
    - receiver: slack-growth
  # teams below route alerts from the platform and data Prometheus servers
  - 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
  # security-ops wanted tickets in Slack as well as Jira (OPS-2263)
  - 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
    # tickets and warnings per pod in Slack, so the channel shows which pod; pages group per service above
    - receiver: slack-security-ops
      group_by: [alertname, pod, service]
  - matchers:
    - team="build-infra"
    receiver: slack-build-infra
    group_wait: 10s
    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="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="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="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
  # messaging asked for hourly repeats while something is still firing
  - matchers:
    - team="messaging"
    receiver: slack-messaging
    repeat_interval: 1h
    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="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
    routes:
    - matchers:
      - severity=~"page|critical"
      receiver: pagerduty-platform
      continue: true
    - matchers:
      - severity="ticket"
      receiver: jira-platform
      continue: true
    - receiver: slack-platform
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.halde.example/hooks/build_infra
- name: pagerduty-checkout-core
  pagerduty_configs:
  - routing_key_file: /etc/alertmanager/secrets/pagerduty/checkout-core
- name: slack-checkout-core
  slack_configs:
  - channel: "#checkout-core-alerts"
    send_resolved: true
- name: jira-checkout-core
  webhook_configs:
  - url: https://jira-bridge.halde.example/hooks/checkout_core
- 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.halde.example/hooks/data_platform
# routing key rotated in OPS-2711
- 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.halde.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.halde.example/hooks/edge
- name: pagerduty-fulfillment
  pagerduty_configs:
  - routing_key_file: /etc/alertmanager/secrets/pagerduty/fulfillment
- name: slack-fulfillment
  slack_configs:
  - channel: "#fulfillment-alerts"
    send_resolved: true
- name: jira-fulfillment
  webhook_configs:
  - url: https://jira-bridge.halde.example/hooks/fulfillment
- name: pagerduty-growth
  pagerduty_configs:
  - routing_key_file: /etc/alertmanager/secrets/pagerduty/growth
- name: slack-growth
  slack_configs:
  - channel: "#growth-alerts"
    send_resolved: true
- name: jira-growth
  webhook_configs:
  - url: https://jira-bridge.halde.example/hooks/growth
- 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.halde.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.halde.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.halde.example/hooks/network
- 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.halde.example/hooks/platform
- 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.halde.example/hooks/security_ops
- 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.halde.example/hooks/storage
- name: pagerduty-storefront
  pagerduty_configs:
  - routing_key_file: /etc/alertmanager/secrets/pagerduty/storefront
- name: slack-storefront
  slack_configs:
  - channel: "#storefront-alerts"
    send_resolved: true
- name: jira-storefront
  webhook_configs:
  - url: https://jira-bridge.halde.example/hooks/storefront
# unused since 2024, the SMTP relay it points at is gone
- name: email-oncall
  email_configs:
  - to: oncall@halde.example
    send_resolved: false
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="ClusterUnreachable"
  target_matchers:
  - service=~".+"
  equal: [cluster]
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.halde.example/alerts/HostDiskAlmostFull
AF_EOF
mkdir -p 'rules'
cat > 'rules/legacy-checkout-core.yml' <<'AF_EOF'
# checkout-core 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: checkout-core-records
  rules:
  - record: job:http_requests:rate5m
    expr: sum by (job, service) (rate(http_requests_total{service=~"checkout-api|order-events"}[5m]))
  - record: job:http_errors:rate5m
    expr: sum by (job, service) (rate(http_requests_total{service=~"checkout-api|order-events",code=~"5.."}[5m]))
- name: checkout-api
  rules:
  # threshold agreed with checkout-core in OPS-1811
  - alert: CheckoutApiHighErrorRatio
    expr: sum by (service) (rate(http_requests_total{service="checkout-api",code=~"5.."}[5m])) / sum by (service) (rate(http_requests_total{service="checkout-api"}[5m])) > 0.05
    for: "10m"
    labels: {severity: page, team: checkout-core}
    annotations:
      summary: "{{ $labels.service }} is failing {{ $value | humanizePercentage }} of requests"
      runbook_url: https://runbooks.halde.example/alerts/CheckoutApiHighErrorRatio
  - alert: CheckoutApiLatencyHigh
    expr: histogram_quantile(0.99, sum by (service, le) (rate(http_request_duration_seconds_bucket{service="checkout-api"}[5m]))) > 0.5
    for: "10m"
    labels: {severity: warning, team: checkout-core}
    annotations:
      summary: "{{ $labels.service }} p99 above 500ms"
      runbook_url: https://runbooks.halde.example/alerts/CheckoutApiLatencyHigh
  - alert: CheckoutApiLatencyHigh
    expr: histogram_quantile(0.99, sum by (service, le) (rate(http_request_duration_seconds_bucket{service="checkout-api"}[5m]))) > 1
    for: "10m"
    labels: {severity: critical, team: checkout-core}
    annotations:
      summary: "{{ $labels.service }} p99 above 1s"
      runbook_url: https://runbooks.halde.example/alerts/CheckoutApiLatencyHigh
  - alert: DbClientConnectionErrors
    expr: rate(db_client_connection_errors_total{service="checkout-api"}[2m]) > 0.5
    for: "2m"
    labels: {severity: page, team: checkout-core}
    annotations:
      summary: "{{ $labels.pod }} can't get database connections"
      runbook_url: https://runbooks.halde.example/alerts/DbClientConnectionErrors
  # average the pods: they all run with the same limit, so the mean is what we size it by
  - alert: CheckoutApiCpuThrottled
    expr: avg by (service) (rate(container_cpu_cfs_throttled_periods_total{service="checkout-api",container="checkout-api"}[5m]) / rate(container_cpu_cfs_periods_total{service="checkout-api",container="checkout-api"}[5m])) > 0.25
    for: "30m"
    labels: {severity: ticket, team: checkout-core}
    annotations:
      summary: "{{ $labels.service }} pods spend over a quarter of their CPU periods throttled"
      runbook_url: https://runbooks.halde.example/alerts/CheckoutApiCpuThrottled
- name: order-events
  rules:
  - alert: OrderEventsHighErrorRatio
    expr: sum by (service) (rate(http_requests_total{service="order-events",code=~"5.."}[5m])) / sum by (service) (rate(http_requests_total{service="order-events"}[5m])) > 0.1
    for: "10m"
    labels: {severity: page, team: checkout-core}
    annotations:
      summary: "{{ $labels.service }} is failing {{ $value | humanizePercentage }} of requests"
      runbook_url: https://runbooks.halde.example/alerts/OrderEventsHighErrorRatio
  - alert: OrderEventsLatencyHigh
    expr: histogram_quantile(0.99, sum by (service, le) (rate(http_request_duration_seconds_bucket{service="order-events"}[5m]))) > 0.5
    for: "10m"
    labels: {severity: warning, team: checkout-core}
    annotations:
      summary: "{{ $labels.service }} p99 above 500ms"
      runbook_url: https://runbooks.halde.example/alerts/OrderEventsLatencyHigh
  - alert: OrderEventsLatencyHigh
    expr: histogram_quantile(0.99, sum by (service, le) (rate(http_request_duration_seconds_bucket{service="order-events"}[5m]))) > 1
    for: "10m"
    labels: {severity: critical, team: checkout-core}
    annotations:
      summary: "{{ $labels.service }} p99 above 1s"
      runbook_url: https://runbooks.halde.example/alerts/OrderEventsLatencyHigh
  - alert: OrderEventsQueueBacklogHigh
    expr: max by (service) (work_queue_depth{service="order-events"}) > 5000
    for: "15m"
    labels: {severity: page, team: checkout-core}
    annotations:
      summary: "{{ $labels.service }} has more than 5000 jobs waiting"
      runbook_url: https://runbooks.halde.example/alerts/OrderEventsQueueBacklogHigh
AF_EOF
mkdir -p 'rules'
cat > 'rules/legacy-storefront.yml' <<'AF_EOF'
# storefront 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: storefront-records
  rules:
  - record: job:http_requests:rate5m
    expr: sum by (job, service) (rate(http_requests_total{service=~"returns-api|cart-svc"}[5m]))
  - record: job:http_errors:rate5m
    expr: sum by (job, service) (rate(http_requests_total{service=~"returns-api|cart-svc",code=~"5.."}[5m]))
- name: returns-api
  rules:
  # threshold agreed with storefront in OPS-1584
  - alert: ReturnsApiHighErrorRatio
    expr: sum by (service) (rate(http_requests_total{service="returns-api",code=~"5.."}[5m])) / sum by (service) (rate(http_requests_total{service="returns-api"}[5m])) > 0.1
    for: "10m"
    labels: {severity: page, team: storefront}
    annotations:
      summary: "{{ $labels.service }} is failing {{ $value | humanizePercentage }} of requests"
      runbook_url: https://runbooks.halde.example/alerts/ReturnsApiHighErrorRatio
  - alert: ReturnsApiLatencyHigh
    expr: histogram_quantile(0.99, sum by (service, le) (rate(http_request_duration_seconds_bucket{service="returns-api"}[5m]))) > 0.5
    for: "10m"
    labels: {severity: warning, team: storefront}
    annotations:
      summary: "{{ $labels.service }} p99 above 500ms"
      runbook_url: https://runbooks.halde.example/alerts/ReturnsApiLatencyHigh
  # TODO(2024) move to a latency SLO once we have one
  - alert: ReturnsApiLatencyHigh
    expr: histogram_quantile(0.99, sum by (service, le) (rate(http_request_duration_seconds_bucket{service="returns-api"}[5m]))) > 1
    for: "10m"
    labels: {severity: critical, team: storefront}
    annotations:
      summary: "{{ $labels.service }} p99 above 1s"
      runbook_url: https://runbooks.halde.example/alerts/ReturnsApiLatencyHigh
  - alert: ReturnsApiDbConnectionsHigh
    expr: max by (service) (db_pool_connections_active{service="returns-api"} / db_pool_connections_max{service="returns-api"}) > 0.8
    for: "5m"
    labels: {severity: warning, team: storefront}
    annotations:
      summary: "{{ $labels.service }} is using over 80% of its DB pool"
      runbook_url: https://runbooks.halde.example/alerts/ReturnsApiDbConnectionsHigh
  - alert: ReturnsApiDbConnectionsHigh
    expr: max by (service) (db_pool_connections_active{service="returns-api"} / db_pool_connections_max{service="returns-api"}) > 0.95
    for: "5m"
    labels: {severity: critical, team: storefront}
    annotations:
      summary: "{{ $labels.service }} DB pool nearly exhausted"
      runbook_url: https://runbooks.halde.example/alerts/ReturnsApiDbConnectionsHigh
  - alert: DbClientConnectionErrors
    expr: rate(db_client_connection_errors_total{service="returns-api"}[2m]) > 0.5
    for: "2m"
    labels: {severity: page, team: storefront}
    annotations:
      summary: "{{ $labels.pod }} can't get database connections"
      runbook_url: https://runbooks.halde.example/alerts/DbClientConnectionErrors
- name: cart-svc
  rules:
  - alert: CartSvcHighErrorRatio
    expr: sum by (service) (rate(http_requests_total{service="cart-svc",code=~"5.."}[5m])) / sum by (service) (rate(http_requests_total{service="cart-svc"}[5m])) > 0.02
    for: "10m"
    labels: {severity: page, team: storefront}
    annotations:
      summary: "{{ $labels.service }} is failing {{ $value | humanizePercentage }} of requests"
      runbook_url: https://runbooks.halde.example/alerts/CartSvcHighErrorRatio
  - alert: CartSvcLatencyHigh
    expr: histogram_quantile(0.99, sum by (service, le) (rate(http_request_duration_seconds_bucket{service="cart-svc"}[5m]))) > 0.5
    for: "10m"
    labels: {severity: warning, team: storefront}
    annotations:
      summary: "{{ $labels.service }} p99 above 500ms"
      runbook_url: https://runbooks.halde.example/alerts/CartSvcLatencyHigh
  # TODO(2024) move to a latency SLO once we have one
  - alert: CartSvcLatencyHigh
    expr: histogram_quantile(0.99, sum by (service, le) (rate(http_request_duration_seconds_bucket{service="cart-svc"}[5m]))) > 1
    for: "10m"
    labels: {severity: critical, team: storefront}
    annotations:
      summary: "{{ $labels.service }} p99 above 1s"
      runbook_url: https://runbooks.halde.example/alerts/CartSvcLatencyHigh
  - alert: CartSvcDbConnectionsHigh
    expr: max by (service) (db_pool_connections_active{service="cart-svc"} / db_pool_connections_max{service="cart-svc"}) > 0.8
    for: "5m"
    labels: {severity: warning, team: storefront}
    annotations:
      summary: "{{ $labels.service }} is using over 80% of its DB pool"
      runbook_url: https://runbooks.halde.example/alerts/CartSvcDbConnectionsHigh
  - alert: CartSvcDbConnectionsHigh
    expr: max by (service) (db_pool_connections_active{service="cart-svc"} / db_pool_connections_max{service="cart-svc"}) > 0.95
    for: "5m"
    labels: {severity: critical, team: storefront}
    annotations:
      summary: "{{ $labels.service }} DB pool nearly exhausted"
      runbook_url: https://runbooks.halde.example/alerts/CartSvcDbConnectionsHigh
  - alert: DbClientConnectionErrors
    expr: rate(db_client_connection_errors_total{service="cart-svc"}[2m]) > 0.5
    for: "2m"
    labels: {severity: page, team: storefront}
    annotations:
      summary: "{{ $labels.pod }} can't get database connections"
      runbook_url: https://runbooks.halde.example/alerts/DbClientConnectionErrors
AF_EOF