partial/afx-e2-s07/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
  # ingest: still on the old match syntax
  - match:
      team: ingest
    receiver: slack-ingest
    routes:
    - match_re:
        severity: page|critical
      receiver: pagerduty-ingest
      continue: true
    - match:
        severity: ticket
      receiver: jira-ingest
      continue: true
    - receiver: slack-ingest
  - matchers:
    - team="subscriptions"
    receiver: slack-subscriptions
    routes:
    - matchers:
      - severity=~"page|critical"
      receiver: pagerduty-subscriptions
      continue: true
    - matchers:
      - severity="ticket"
      receiver: jira-subscriptions
      continue: true
    # tickets and warnings per pod in Slack, so the channel shows which pod; pages group per service above
    - receiver: slack-subscriptions
      group_by: [alertname, pod, service]
  - matchers:
    - team="discovery"
    receiver: slack-discovery
    routes:
    - matchers:
      - severity=~"page|critical"
      receiver: pagerduty-discovery
      continue: true
    - matchers:
      - severity="ticket"
      receiver: jira-discovery
      continue: true
    - receiver: slack-discovery
  - matchers:
    - team="playback"
    receiver: slack-playback
    routes:
    - matchers:
      - severity=~"page|critical"
      receiver: pagerduty-playback
      continue: true
    - matchers:
      - severity="ticket"
      receiver: jira-playback
      continue: true
    - receiver: slack-playback
  - matchers:
    - team="content-pipeline"
    receiver: slack-content-pipeline
    routes:
    - matchers:
      - severity=~"page|critical"
      receiver: pagerduty-content-pipeline
      continue: true
    - matchers:
      - severity="ticket"
      receiver: jira-content-pipeline
      continue: true
    - receiver: slack-content-pipeline
  # discovery services from before team labels were everywhere
  - matchers:
    - service=~"search-indexer|catalog-svc|recs-svc"
    receiver: slack-discovery
    routes:
    - matchers:
      - severity=~"page|critical"
      receiver: pagerduty-discovery
      continue: true
    - receiver: slack-discovery
  - matchers:
    - team="rights"
    receiver: slack-rights
    routes:
    - matchers:
      - severity=~"page|critical"
      receiver: pagerduty-rights
      continue: true
    - matchers:
      - severity="ticket"
      receiver: jira-rights
      continue: true
    - receiver: slack-rights
  # teams below route alerts from the platform and data Prometheus servers
  - 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="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
  # network: fewer updates per group, too chatty at 5m
  - 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
  # 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="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
  # edge wanted tickets in Slack as well as Jira (INFRA-1201)
  - 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="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-content-pipeline
  pagerduty_configs:
  - routing_key_file: /etc/alertmanager/secrets/pagerduty/content-pipeline
- name: slack-content-pipeline
  slack_configs:
  - channel: "#content-pipeline-alerts"
    send_resolved: true
- name: jira-content-pipeline
  webhook_configs:
  - url: https://jira-bridge.int.ondaplay.example/hooks/content_pipeline
- 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.int.ondaplay.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.int.ondaplay.example/hooks/database_reliability
- name: pagerduty-discovery
  pagerduty_configs:
  - routing_key_file: /etc/alertmanager/secrets/pagerduty/discovery
- name: slack-discovery
  slack_configs:
  - channel: "#discovery-alerts"
    send_resolved: true
- name: jira-discovery
  webhook_configs:
  - url: https://jira-bridge.int.ondaplay.example/hooks/discovery
- 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.int.ondaplay.example/hooks/edge
- name: pagerduty-ingest
  pagerduty_configs:
  - routing_key_file: /etc/alertmanager/secrets/pagerduty/ingest
- name: slack-ingest
  slack_configs:
  - channel: "#ingest-alerts"
    send_resolved: true
- name: jira-ingest
  webhook_configs:
  - url: https://jira-bridge.int.ondaplay.example/hooks/ingest
- 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.int.ondaplay.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.int.ondaplay.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.int.ondaplay.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.int.ondaplay.example/hooks/platform
- name: pagerduty-playback
  pagerduty_configs:
  - routing_key_file: /etc/alertmanager/secrets/pagerduty/playback
- name: slack-playback
  slack_configs:
  - channel: "#playback-alerts"
    send_resolved: true
- name: jira-playback
  webhook_configs:
  - url: https://jira-bridge.int.ondaplay.example/hooks/playback
- name: pagerduty-rights
  pagerduty_configs:
  - routing_key_file: /etc/alertmanager/secrets/pagerduty/rights
- name: slack-rights
  slack_configs:
  - channel: "#rights-alerts"
    send_resolved: true
- name: jira-rights
  webhook_configs:
  - url: https://jira-bridge.int.ondaplay.example/hooks/rights
- 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.int.ondaplay.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.int.ondaplay.example/hooks/storage
- name: pagerduty-subscriptions
  pagerduty_configs:
  - routing_key_file: /etc/alertmanager/secrets/pagerduty/subscriptions
- name: slack-subscriptions
  slack_configs:
  - channel: "#subscriptions-alerts"
    send_resolved: true
- name: jira-subscriptions
  webhook_configs:
  - url: https://jira-bridge.int.ondaplay.example/hooks/subscriptions
# 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/legacy-content-pipeline.yml' <<'AF_EOF'
# content-pipeline 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: content-pipeline-records
  rules:
  - record: job:http_requests:rate5m
    expr: sum by (job, service) (rate(http_requests_total{service=~"subtitle-svc|transcode-worker"}[5m]))
  - record: job:http_errors:rate5m
    expr: sum by (job, service) (rate(http_requests_total{service=~"subtitle-svc|transcode-worker",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: subtitle-svc
  rules:
  - alert: SubtitleSvcHighErrorRatio
    expr: sum by (service) (rate(http_requests_total{service="subtitle-svc",code=~"5.."}[5m])) / sum by (service) (rate(http_requests_total{service="subtitle-svc"}[5m])) > 0.1
    for: "10m"
    labels: {severity: page, team: content-pipeline}
    annotations:
      summary: "{{ $labels.service }} is failing {{ $value | humanizePercentage }} of requests"
      runbook_url: https://runbooks.int.ondaplay.example/alerts/SubtitleSvcHighErrorRatio
  - alert: SubtitleSvcLatencyHigh
    expr: histogram_quantile(0.99, sum by (service, le) (rate(http_request_duration_seconds_bucket{service="subtitle-svc"}[5m]))) > 0.5
    for: "10m"
    labels: {severity: warning, team: content-pipeline}
    annotations:
      summary: "{{ $labels.service }} p99 above 500ms"
      runbook_url: https://runbooks.int.ondaplay.example/alerts/SubtitleSvcLatencyHigh
  - alert: SubtitleSvcLatencyHigh
    expr: histogram_quantile(0.99, sum by (service, le) (rate(http_request_duration_seconds_bucket{service="subtitle-svc"}[5m]))) > 1
    for: "10m"
    labels: {severity: critical, team: content-pipeline}
    annotations:
      summary: "{{ $labels.service }} p99 above 1s"
      runbook_url: https://runbooks.int.ondaplay.example/alerts/SubtitleSvcLatencyHigh
  - alert: SubtitleSvcDbConnectionsHigh
    expr: max by (service) (db_pool_connections_active{service="subtitle-svc"} / db_pool_connections_max{service="subtitle-svc"}) > 0.8
    for: "5m"
    labels: {severity: warning, team: content-pipeline}
    annotations:
      summary: "{{ $labels.service }} is using over 80% of its DB pool"
      runbook_url: https://wiki.int.ondaplay.example/display/INFRA/SubtitleSvcDbConnectionsHigh+runbook
  - alert: SubtitleSvcDbConnectionsHigh
    expr: max by (service) (db_pool_connections_active{service="subtitle-svc"} / db_pool_connections_max{service="subtitle-svc"}) > 0.95
    for: "5m"
    labels: {severity: critical, team: content-pipeline}
    annotations:
      summary: "{{ $labels.service }} DB pool nearly exhausted"
      runbook_url: https://wiki.int.ondaplay.example/display/INFRA/SubtitleSvcDbConnectionsHigh+runbook
  - alert: DbClientConnectionErrors
    expr: rate(db_client_connection_errors_total{service="subtitle-svc"}[2m]) > 0.5
    for: "2m"
    labels: {severity: page, team: content-pipeline}
    annotations:
      summary: "{{ $labels.pod }} can't get database connections"
      runbook_url: https://runbooks.int.ondaplay.example/alerts/DbClientConnectionErrors
  - alert: SubtitleSvcErrorBurst
    expr: sum by (service) (rate(http_requests_total{service="subtitle-svc",code=~"5.."}[5m])) > 4
    for: "10m"
    labels: {severity: page, team: content-pipeline}
    annotations:
      summary: "{{ $labels.service }} is returning more than 4 errors/s"
      runbook_url: https://runbooks.int.ondaplay.example/alerts/SubtitleSvcErrorBurst
- name: transcode-worker
  rules:
  - alert: TranscodeWorkerHighErrorRatio
    expr: sum by (service) (rate(http_requests_total{service="transcode-worker",code=~"5.."}[5m])) / sum by (service) (rate(http_requests_total{service="transcode-worker"}[5m])) > 0.1
    for: "10m"
    labels: {severity: page, team: content-pipeline}
    annotations:
      summary: "{{ $labels.service }} is failing {{ $value | humanizePercentage }} of requests"
      runbook_url: https://runbooks.int.ondaplay.example/alerts/TranscodeWorkerHighErrorRatio
  - alert: DbClientConnectionErrors
    expr: rate(db_client_connection_errors_total{service="transcode-worker"}[2m]) > 0.5
    for: "2m"
    labels: {severity: page, team: content-pipeline}
    annotations:
      summary: "{{ $labels.pod }} can't get database connections"
      runbook_url: https://runbooks.int.ondaplay.example/alerts/DbClientConnectionErrors
  - alert: TranscodeWorkerQueueBacklogHigh
    expr: max by (service) (work_queue_depth{service="transcode-worker"}) > 5000
    for: "15m"
    labels: {severity: page, team: content-pipeline}
    annotations:
      summary: "{{ $labels.service }} has more than 5000 jobs waiting"
      runbook_url: https://runbooks.int.ondaplay.example/alerts/TranscodeWorkerQueueBacklogHigh
AF_EOF
mkdir -p 'rules'
cat > 'rules/legacy-playback.yml' <<'AF_EOF'
# playback 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: playback-records
  rules:
  - record: job:http_requests:rate5m
    expr: sum by (job, service) (rate(http_requests_total{service="playback-api"}[5m]))
  - record: job:http_errors:rate5m
    expr: sum by (job, service) (rate(http_requests_total{service="playback-api",code=~"5.."}[5m]))
- name: playback-api
  rules:
  # threshold agreed with playback in INFRA-1871
  - alert: PlaybackApiHighErrorRatio
    expr: avg by (service) (sum by (service, pod) (rate(http_requests_total{service="playback-api",pod!~".*canary.*",code=~"5.."}[5m])) / sum by (service, pod) (rate(http_requests_total{service="playback-api"}[5m]))) > 0.05
    for: "10m"
    labels: {severity: page, team: playback}
    annotations:
      summary: "{{ $labels.service }} is failing {{ $value | humanizePercentage }} of requests"
      runbook_url: https://runbooks.int.ondaplay.example/alerts/PlaybackApiHighErrorRatio
  - alert: PlaybackApiLatencyHigh
    expr: histogram_quantile(0.99, sum by (service, le) (rate(http_request_duration_seconds_bucket{service="playback-api"}[5m]))) > 0.5
    for: "10m"
    labels: {severity: warning, team: playback}
    annotations:
      summary: "{{ $labels.service }} p99 above 500ms"
      runbook_url: https://runbooks.int.ondaplay.example/alerts/PlaybackApiLatencyHigh
  - alert: PlaybackApiLatencyHigh
    expr: histogram_quantile(0.99, sum by (service, le) (rate(http_request_duration_seconds_bucket{service="playback-api"}[5m]))) > 1
    for: "10m"
    labels: {severity: critical, team: playback}
    annotations:
      summary: "{{ $labels.service }} p99 above 1s"
      runbook_url: https://runbooks.int.ondaplay.example/alerts/PlaybackApiLatencyHigh
  - alert: PlaybackApiDbConnectionsHigh
    expr: max by (service) (db_pool_connections_active{service="playback-api"} / db_pool_connections_max{service="playback-api"}) > 0.8
    for: "5m"
    labels: {severity: warning, team: playback}
    annotations:
      summary: "{{ $labels.service }} is using over 80% of its DB pool"
      runbook_url: https://runbooks.int.ondaplay.example/alerts/PlaybackApiDbConnectionsHigh
  - alert: PlaybackApiDbConnectionsHigh
    expr: max by (service) (db_pool_connections_active{service="playback-api"} / db_pool_connections_max{service="playback-api"}) > 0.95
    for: "5m"
    labels: {severity: critical, team: playback}
    annotations:
      summary: "{{ $labels.service }} DB pool nearly exhausted"
      runbook_url: https://runbooks.int.ondaplay.example/alerts/PlaybackApiDbConnectionsHigh
  - alert: DbClientConnectionErrors
    expr: rate(db_client_connection_errors_total{service="playback-api"}[2m]) > 0.5
    for: "2m"
    labels: {severity: page, team: playback}
    annotations:
      summary: "{{ $labels.pod }} can't get database connections"
      runbook_url: https://runbooks.int.ondaplay.example/alerts/DbClientConnectionErrors
AF_EOF