partial/afx-e2-s09/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:
    - alertname="ClusterUnreachable"
    receiver: pagerduty-platform
  - matchers:
    - team="payments-core"
    receiver: slack-payments-core
    routes:
    - matchers:
      - severity=~"page|critical"
      receiver: pagerduty-payments-core
      continue: true
    - matchers:
      - severity="ticket"
      receiver: jira-payments-core
      continue: true
    - receiver: slack-payments-core
  - matchers:
    - team="onboarding"
    receiver: slack-onboarding
    routes:
    - matchers:
      - severity=~"page|critical"
      receiver: pagerduty-onboarding
      continue: true
    - matchers:
      - severity="ticket"
      receiver: jira-onboarding
      continue: true
    - receiver: slack-onboarding
  - matchers:
    - team="treasury"
    receiver: slack-treasury
    routes:
    - matchers:
      - severity=~"page|critical"
      receiver: pagerduty-treasury
      continue: true
    - matchers:
      - severity="ticket"
      receiver: jira-treasury
      continue: true
    - receiver: slack-treasury
  - matchers:
    - team="ledger"
    receiver: slack-ledger
    routes:
    - matchers:
      - severity=~"page|critical"
      receiver: pagerduty-ledger
      continue: true
    - matchers:
      - severity="ticket"
      receiver: jira-ledger
      continue: true
    - receiver: slack-ledger
  # risk: still on the old match syntax
  - match:
      team: risk
    receiver: slack-risk
    routes:
    - match_re:
        severity: page|critical
      receiver: pagerduty-risk
      continue: true
    - match:
        severity: ticket
      receiver: jira-risk
      continue: true
    - receiver: slack-risk
  # payments-core services from before team labels were everywhere
  - matchers:
    - service=~"wallet-svc|payments-gw|card-auth"
    receiver: slack-payments-core
    routes:
    - matchers:
      - severity=~"page|critical"
      receiver: pagerduty-payments-core
      continue: true
    - receiver: slack-payments-core
  # teams below route alerts from the platform and data Prometheus servers
  - matchers:
    - team="build-infra"
    receiver: slack-build-infra
    repeat_interval: 1h
    routes:
    - matchers:
      - severity=~"page|critical"
      receiver: pagerduty-build-infra
      continue: true
    - matchers:
      - severity="ticket"
      receiver: jira-build-infra
      continue: true
    - receiver: slack-build-infra
  # messaging wanted tickets in Slack as well as Jira (INFRA-2302)
  - 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="database-reliability"
    receiver: slack-database-reliability
    group_wait: 10s
    routes:
    - matchers:
      - severity=~"page|critical"
      receiver: pagerduty-database-reliability
      continue: true
    - matchers:
      - severity="ticket"
      receiver: jira-database-reliability
      continue: true
    # tickets and warnings per pod in Slack, so the channel shows which pod; pages group per service above
    - receiver: slack-database-reliability
      group_by: [alertname, pod, service]
  - 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="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="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="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
  - 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.int.trevopag.example/hooks/build_infra
- name: pagerduty-cards
  pagerduty_configs:
  - routing_key_file: /etc/alertmanager/secrets/pagerduty/cards
- name: slack-cards
  slack_configs:
  - channel: "#cards-alerts"
    send_resolved: true
- name: jira-cards
  webhook_configs:
  - url: https://jira-bridge.int.trevopag.example/hooks/cards
- 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.trevopag.example/hooks/database_reliability
- name: pagerduty-ledger
  pagerduty_configs:
  - routing_key_file: /etc/alertmanager/secrets/pagerduty/ledger
- name: slack-ledger
  slack_configs:
  - channel: "#ledger-alerts"
    send_resolved: true
- name: jira-ledger
  webhook_configs:
  - url: https://jira-bridge.int.trevopag.example/hooks/ledger
- 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.trevopag.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.trevopag.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.trevopag.example/hooks/network
- name: pagerduty-onboarding
  pagerduty_configs:
  - routing_key_file: /etc/alertmanager/secrets/pagerduty/onboarding
- name: slack-onboarding
  slack_configs:
  - channel: "#onboarding-alerts"
    send_resolved: true
- name: jira-onboarding
  webhook_configs:
  - url: https://jira-bridge.int.trevopag.example/hooks/onboarding
- name: pagerduty-payments-core
  pagerduty_configs:
  - routing_key_file: /etc/alertmanager/secrets/pagerduty/payments-core
- name: slack-payments-core
  slack_configs:
  - channel: "#payments-core-alerts"
    send_resolved: true
- name: jira-payments-core
  webhook_configs:
  - url: https://jira-bridge.int.trevopag.example/hooks/payments_core
- 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.trevopag.example/hooks/platform
- name: pagerduty-risk
  pagerduty_configs:
  - routing_key_file: /etc/alertmanager/secrets/pagerduty/risk
- name: slack-risk
  slack_configs:
  - channel: "#risk-alerts"
    send_resolved: true
- name: jira-risk
  webhook_configs:
  - url: https://jira-bridge.int.trevopag.example/hooks/risk
- 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.trevopag.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.trevopag.example/hooks/storage
# routing key rotated in INFRA-2887
- name: pagerduty-treasury
  pagerduty_configs:
  - routing_key_file: /etc/alertmanager/secrets/pagerduty/treasury
- name: slack-treasury
  slack_configs:
  - channel: "#treasury-alerts"
    send_resolved: true
- name: jira-treasury
  webhook_configs:
  - url: https://jira-bridge.int.trevopag.example/hooks/treasury
# nothing routes here since the rota moved to PagerDuty; ask before deleting
- name: slack-old-oncall
  slack_configs:
  - channel: "#oncall-old"
    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="ClusterUnreachable"
  target_matchers:
  - alertname=~"LedgerApiDown|WalletSvcDown|LedgerWorkerDown|StatementsExportDown|FxRatesDown|KycSvcDown|PaymentsGwDown|FraudScorerDown"
  equal: [cluster]
AF_EOF
mkdir -p 'rules'
cat > 'rules/legacy-onboarding.yml' <<'AF_EOF'
# onboarding 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: onboarding-records
  rules:
  - record: job:http_requests:rate5m
    expr: sum by (job, service) (rate(http_requests_total{service="kyc-svc"}[5m]))
  - record: job:http_errors:rate5m
    expr: sum by (job, service) (rate(http_requests_total{service="kyc-svc",code=~"5.."}[5m]))
- name: kyc-svc
  rules:
  - alert: KycSvcHighErrorRatio
    expr: sum by (service) (rate(http_requests_total{service="kyc-svc",code=~"5.."}[5m])) / sum by (service) (rate(http_requests_total{service="kyc-svc"}[5m])) > 0.1
    for: "10m"
    labels: {severity: page, team: onboarding}
    annotations:
      summary: "{{ $labels.service }} is failing {{ $value | humanizePercentage }} of requests"
      runbook_url: https://runbooks.int.trevopag.example/alerts/KycSvcHighErrorRatio
  - alert: KycSvcLatencyHigh
    expr: histogram_quantile(0.99, sum by (service, le) (rate(http_request_duration_seconds_bucket{service="kyc-svc"}[5m]))) > 0.5
    for: "10m"
    labels: {severity: warning, team: onboarding}
    annotations:
      summary: "{{ $labels.service }} p99 above 500ms"
      runbook_url: https://runbooks.int.trevopag.example/alerts/KycSvcLatencyHigh
  - alert: KycSvcLatencyHigh
    expr: histogram_quantile(0.99, sum by (service, le) (rate(http_request_duration_seconds_bucket{service="kyc-svc"}[5m]))) > 1
    for: "10m"
    labels: {severity: critical, team: onboarding}
    annotations:
      summary: "{{ $labels.service }} p99 above 1s"
      runbook_url: https://runbooks.int.trevopag.example/alerts/KycSvcLatencyHigh
  - alert: KycSvcDbConnectionsHigh
    expr: max by (service) (db_pool_connections_active{service="kyc-svc"} / db_pool_connections_max{service="kyc-svc"}) > 0.8
    for: "5m"
    labels: {severity: warning, team: onboarding}
    annotations:
      summary: "{{ $labels.service }} is using over 80% of its DB pool"
      runbook_url: https://runbooks.int.trevopag.example/alerts/KycSvcDbConnectionsHigh
  - alert: KycSvcDbConnectionsHigh
    expr: max by (service) (db_pool_connections_active{service="kyc-svc"} / db_pool_connections_max{service="kyc-svc"}) > 0.95
    for: "5m"
    labels: {severity: critical, team: onboarding}
    annotations:
      summary: "{{ $labels.service }} DB pool nearly exhausted"
      runbook_url: https://runbooks.int.trevopag.example/alerts/KycSvcDbConnectionsHigh
  # average the pods: they all run with the same limit, so the mean is what we size it by
  - alert: KycSvcCpuThrottled
    expr: avg by (service) (rate(container_cpu_cfs_throttled_periods_total{service="kyc-svc",container="kyc-svc"}[5m]) / rate(container_cpu_cfs_periods_total{service="kyc-svc",container="kyc-svc"}[5m])) > 0.25
    for: "30m"
    labels: {severity: ticket, team: onboarding}
    annotations:
      summary: "{{ $labels.service }} pods spend over a quarter of their CPU periods throttled"
      runbook_url: https://runbooks.int.trevopag.example/alerts/KycSvcCpuThrottled
AF_EOF
mkdir -p 'rules'
cat > 'rules/payments-core-rules.yaml' <<'AF_EOF'
apiVersion: monitoring.coreos.com/v1
kind: PrometheusRule
metadata:
  name: payments-core-rules
  namespace: monitoring
  labels:
    role: alert-rules
spec:
  groups:
  - name: card-auth
    rules:
    - alert: CardAuthDown
      expr: |
        sum by (service, cluster) (up{service="card-auth"}) == 0
        or absent(up{service="card-auth"})
      for: 3m
      labels:
        severity: page
        team: cards
      annotations:
        summary: card-auth has no healthy scrape targets
        runbook_url: https://runbooks.int.trevopag.example/alerts/CardAuthDown
    - alert: CardAuthHighErrorRatio
      expr: |
        sum by (service) (rate(http_requests_total{service="card-auth",code=~"5.."}[5m]))
        / sum by (service) (rate(http_requests_total{service="card-auth"}[5m])) > 0.02
      for: 10m
      labels:
        severity: page
        team: cards
      annotations:
        summary: "{{ $labels.service }} is failing {{ $value | humanizePercentage }} of requests"
        runbook_url: https://runbooks.int.trevopag.example/alerts/CardAuthHighErrorRatio
    - alert: CardAuthErrorBudgetBurnFast
      expr: |
        slo:sli_error:ratio_rate1h{service="card-auth"} > (14.4 * 0.0005)
        and slo:sli_error:ratio_rate5m{service="card-auth"} > (14.4 * 0.0005)
      for: 2m
      labels:
        severity: page
        team: cards
        slo: card-auth-availability
      annotations:
        summary: "{{ $labels.service }} is spending its error budget fast"
        runbook_url: https://runbooks.int.trevopag.example/alerts/CardAuthErrorBudgetBurnFast
    - alert: CardAuthErrorBudgetBurnSlow
      expr: |
        slo:sli_error:ratio_rate6h{service="card-auth"} > (6 * 0.0005)
        and slo:sli_error:ratio_rate30m{service="card-auth"} > (6 * 0.0005)
      for: 15m
      labels:
        severity: ticket
        team: cards
        slo: card-auth-availability
      annotations:
        summary: "{{ $labels.service }} is spending its error budget steadily"
        runbook_url: https://runbooks.int.trevopag.example/alerts/CardAuthErrorBudgetBurnSlow
  - name: wallet-svc
    rules:
    - alert: WalletSvcDown
      expr: |
        sum by (service, cluster) (up{service="wallet-svc"}) == 0
        or absent(up{service="wallet-svc"})
      for: 3m
      labels:
        severity: page
        team: payments-core
      annotations:
        summary: wallet-svc has no healthy scrape targets
        runbook_url: https://runbooks.int.trevopag.example/alerts/WalletSvcDown
    - alert: WalletSvcHighErrorRatio
      expr: |
        sum by (service) (rate(http_requests_total{service="wallet-svc",code=~"5.."}[5m]))
        / sum by (service) (rate(http_requests_total{service="wallet-svc"}[5m])) > 0.02
      for: 10m
      labels:
        severity: page
        team: payments-core
      annotations:
        summary: "{{ $labels.service }} is failing {{ $value | humanizePercentage }} of requests"
        runbook_url: https://runbooks.int.trevopag.example/alerts/WalletSvcHighErrorRatio
    - alert: WalletSvcErrorBudgetBurnFast
      expr: |
        slo:sli_error:ratio_rate1h{service="wallet-svc"} > (14.4 * 0.001)
        and slo:sli_error:ratio_rate5m{service="wallet-svc"} > (14.4 * 0.001)
      for: 2m
      labels:
        severity: page
        team: payments-core
        slo: wallet-svc-availability
      annotations:
        summary: "{{ $labels.service }} is spending its error budget fast"
        runbook_url: https://runbooks.int.trevopag.example/alerts/WalletSvcErrorBudgetBurnFast
    - alert: WalletSvcErrorBudgetBurnSlow
      expr: |
        slo:sli_error:ratio_rate6h{service="wallet-svc"} > (6 * 0.001)
        and slo:sli_error:ratio_rate30m{service="wallet-svc"} > (6 * 0.001)
      for: 15m
      labels:
        severity: ticket
        team: payments-core
        slo: wallet-svc-availability
      annotations:
        summary: "{{ $labels.service }} is spending its error budget steadily"
        runbook_url: https://runbooks.int.trevopag.example/alerts/WalletSvcErrorBudgetBurnSlow
    - alert: DbClientConnectionErrors
      expr: |
        rate(db_client_connection_errors_total{service="wallet-svc"}[2m]) > 0.5
      for: 2m
      labels:
        severity: page
        team: payments-core
      annotations:
        summary: "{{ $labels.pod }} can't get database connections"
        runbook_url: https://runbooks.int.trevopag.example/alerts/DbClientConnectionErrors
  - name: payments-gw
    rules:
    # for: 3m so a rolling restart doesn't page; payments-gw cycles one pod at a time
    - alert: PaymentsGwDown
      expr: |
        sum by (service, cluster) (up{service="payments-gw"}) == 0
        or absent(up{service="payments-gw"})
      for: 3m
      labels:
        severity: page
        team: payments-core
      annotations:
        summary: payments-gw has no healthy scrape targets
        runbook_url: https://runbooks.int.trevopag.example/alerts/PaymentsGwDown
    - alert: PaymentsGwHighErrorRatio
      expr: |
        sum by (service) (rate(http_requests_total{service="payments-gw",code=~"5.."}[5m]))
        / sum by (service) (rate(http_requests_total{service="payments-gw"}[5m])) > 0.02
      for: 10m
      labels:
        severity: page
        team: payments-core
      annotations:
        summary: "{{ $labels.service }} is failing {{ $value | humanizePercentage }} of requests"
        runbook_url: https://runbooks.int.trevopag.example/alerts/PaymentsGwHighErrorRatio
    - alert: PaymentsGwErrorBudgetBurnFast
      expr: |
        slo:sli_error:ratio_rate1h{service="payments-gw"} > (14.4 * 0.005)
        and slo:sli_error:ratio_rate5m{service="payments-gw"} > (14.4 * 0.005)
      for: 2m
      labels:
        severity: page
        team: payments-core
        slo: payments-gw-availability
      annotations:
        summary: "{{ $labels.service }} is spending its error budget fast"
        runbook_url: https://runbooks.int.trevopag.example/alerts/PaymentsGwErrorBudgetBurnFast
    - alert: PaymentsGwErrorBudgetBurnSlow
      expr: |
        slo:sli_error:ratio_rate6h{service="payments-gw"} > (6 * 0.005)
        and slo:sli_error:ratio_rate30m{service="payments-gw"} > (6 * 0.005)
      for: 15m
      labels:
        severity: ticket
        team: payments-core
        slo: payments-gw-availability
      annotations:
        summary: "{{ $labels.service }} is spending its error budget steadily"
        runbook_url: https://runbooks.int.trevopag.example/alerts/PaymentsGwErrorBudgetBurnSlow
AF_EOF