Datasets:

openenvforge
/

3ambench

#!/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
  smtp_smarthost: smtp.numerapay.example:587
  smtp_from: alertmanager@numerapay.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:
    - 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="risk"
    receiver: slack-risk
    routes:
    - matchers:
      - severity=~"page|critical"
      receiver: pagerduty-risk
      continue: true
    - matchers:
      - severity="ticket"
      receiver: jira-risk
      continue: true
    - receiver: slack-risk
  # cards: still on the old match syntax
  - match:
      team: cards
    receiver: slack-cards
    routes:
    - match_re:
        severity: page|critical
      receiver: pagerduty-cards
      continue: true
    - match:
        severity: ticket
      receiver: jira-cards
      continue: true
    - receiver: slack-cards
  - 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="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
  # ledger services from before team labels were everywhere
  - matchers:
    - service=~"ledger-api|statements-export"
    receiver: slack-ledger
    routes:
    - matchers:
      - severity=~"page|critical"
      receiver: pagerduty-ledger
      continue: true
    - receiver: slack-ledger
  - 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
  # teams below route alerts from the platform and data Prometheus servers
  - matchers:
    - team="edge"
    receiver: slack-edge
    group_interval: 10m
    routes:
    - matchers:
      - severity=~"page|critical"
      receiver: pagerduty-edge
      continue: true
    - matchers:
      - severity="ticket"
      receiver: jira-edge
      continue: true
    - receiver: slack-edge
  # database-reliability wanted tickets in Slack as well as Jira (PLAT-1728)
  - 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="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="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
  - matchers:
    - team="messaging"
    receiver: slack-messaging
    routes:
    - matchers:
      - severity=~"page|critical"
      receiver: pagerduty-messaging
      continue: true
    - matchers:
      - severity="ticket"
      receiver: jira-messaging
      continue: true
    # tickets and warnings per pod in Slack, so the channel shows which pod; pages group per service above
    - receiver: slack-messaging
      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
  # build-infra asked for hourly repeats while something is still firing
  - 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
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.numerapay.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.numerapay.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.numerapay.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.numerapay.example/hooks/edge
- 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.numerapay.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.numerapay.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.numerapay.example/hooks/ml_platform
- 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.numerapay.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.numerapay.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.numerapay.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.numerapay.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.numerapay.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.numerapay.example/hooks/storage
- 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.numerapay.example/hooks/treasury
# unused since 2024, the SMTP relay it points at is gone
- name: email-oncall
  email_configs:
  - to: oncall@numerapay.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="LedgerApiDown"
  target_matchers:
  - alertname=~"LedgerApiErrorBudgetBurnFast|LedgerApiErrorBudgetBurnSlow|LedgerApiHighErrorRatio"
  equal: [service]
AF_EOF
mkdir -p 'rules'
cat > 'rules/cards-rules.yaml' <<'AF_EOF'
apiVersion: monitoring.coreos.com/v1
kind: PrometheusRule
metadata:
  name: cards-rules
  namespace: monitoring
  labels:
    role: alert-rules
spec:
  groups:
  - name: card-auth
    rules:
    - alert: CardAuthDown
      expr: |
        sum by (service) (up{service="card-auth"}) == 0
        or absent(up{service="card-auth"})
      for: 1m
      labels:
        severity: page
        team: cards
      annotations:
        summary: card-auth has no healthy scrape targets
        runbook_url: https://runbooks.numerapay.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.05
      for: 10m
      labels:
        severity: page
        team: cards
      annotations:
        summary: "{{ $labels.service }} is failing {{ $value | humanizePercentage }} of requests"
        runbook_url: https://runbooks.numerapay.example/alerts/CardAuthHighErrorRatio
    - alert: CardAuthTrafficBelowFloor
      expr: |
        sum by (service) (rate(http_requests_total{service="card-auth"}[5m])) < 5
        and on (service) sum by (service) (up{service="card-auth"}) > 0
      for: 5m
      labels:
        severity: page
        team: cards
      annotations:
        summary: "{{ $labels.service }} is serving under its traffic floor with its pods up"
        runbook_url: https://runbooks.numerapay.example/alerts/CardAuthTrafficBelowFloor
    - alert: CardAuthErrorBudgetBurnFast
      expr: |
        slo:sli_error:ratio_rate1h{service="card-auth"} > (14.4 * 0.005)
        and slo:sli_error:ratio_rate5m{service="card-auth"} > (14.4 * 0.005)
      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.numerapay.example/alerts/CardAuthErrorBudgetBurnFast
    - alert: CardAuthErrorBudgetBurnSlow
      expr: |
        slo:sli_error:ratio_rate6h{service="card-auth"} > (6 * 0.005)
        and slo:sli_error:ratio_rate30m{service="card-auth"} > (6 * 0.005)
      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.numerapay.example/alerts/CardAuthErrorBudgetBurnSlow
  - name: card-worker
    rules:
    - alert: CardWorkerDown
      expr: |
        sum by (service) (up{service="card-worker"}) == 0
        or absent(up{service="card-worker"})
      for: 1m
      labels:
        severity: page
        team: cards
      annotations:
        summary: card-worker has no healthy scrape targets
        runbook_url: https://runbooks.numerapay.example/alerts/CardWorkerDown
    # 5xx only; 429s are the rate limiter doing its job
    - alert: CardWorkerHighErrorRatio
      expr: |
        sum by (service) (rate(http_requests_total{service="card-worker",code=~"5.."}[5m]))
        / sum by (service) (rate(http_requests_total{service="card-worker"}[5m])) > 0.05
      for: 10m
      labels:
        severity: page
        team: cards
      annotations:
        summary: "{{ $labels.service }} is failing {{ $value | humanizePercentage }} of requests"
        runbook_url: https://runbooks.numerapay.example/alerts/CardWorkerHighErrorRatio
    # average over the targets: half of them gone is a ticket even while the rest carry the load
    - alert: CardWorkerTargetsHalfDown
      expr: |
        avg by (service) (up{service="card-worker"}) < 0.5
        and on (service) count by (service) (up{service="card-worker"}) >= 2
      for: 10m
      labels:
        severity: ticket
        team: cards
      annotations:
        summary: "{{ $labels.service }} has lost half of its targets"
        runbook_url: https://runbooks.numerapay.example/alerts/CardWorkerTargetsHalfDown
AF_EOF
mkdir -p 'rules'
cat > 'rules/legacy-ledger.yml' <<'AF_EOF'
# ledger 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: ledger-records
  rules:
  - record: job:grpc_calls:rate5m
    expr: sum by (job, service) (rate(grpc_server_handled_total{service="fx-rates"}[5m]))
  - record: job:grpc_errors:rate5m
    expr: sum by (job, service) (rate(grpc_server_handled_total{service="fx-rates",grpc_code=~"Unavailable|Internal|DeadlineExceeded|Unknown|DataLoss"}[5m]))
  - record: job:http_requests:rate5m
    expr: sum by (job, service) (rate(http_requests_total{service="ledger-api"}[5m]))
  - record: job:http_errors:rate5m
    expr: sum by (job, service) (rate(http_requests_total{service="ledger-api",code=~"5.."}[5m]))
- name: ledger-api
  rules:
  # threshold agreed with ledger in PLAT-1677
  - alert: LedgerApiHighErrorRatio
    expr: sum by (service) (rate(http_requests_total{service="ledger-api",code=~"5.."}[5m])) / sum by (service) (rate(http_requests_total{service="ledger-api"}[5m])) > 0.02
    for: "10m"
    labels: {severity: page, team: ledger}
    annotations:
      summary: "{{ $labels.service }} is failing {{ $value | humanizePercentage }} of requests"
      runbook_url: https://runbooks.numerapay.example/alerts/LedgerApiHighErrorRatio
  - alert: LedgerApiLatencyHigh
    expr: histogram_quantile(0.99, sum by (service, le) (rate(http_request_duration_seconds_bucket{service="ledger-api"}[5m]))) > 0.5
    for: "10m"
    labels: {severity: warning, team: ledger}
    annotations:
      summary: "{{ $labels.service }} p99 above 500ms"
      runbook_url: https://runbooks.numerapay.example/alerts/LedgerApiLatencyHigh
  - alert: LedgerApiLatencyHigh
    expr: histogram_quantile(0.99, sum by (service, le) (rate(http_request_duration_seconds_bucket{service="ledger-api"}[5m]))) > 1
    for: "10m"
    labels: {severity: critical, team: ledger}
    annotations:
      summary: "{{ $labels.service }} p99 above 1s"
      runbook_url: https://runbooks.numerapay.example/alerts/LedgerApiLatencyHigh
- name: fx-rates
  rules:
  - alert: FxRatesHighErrorRatio
    expr: sum by (service) (rate(grpc_server_handled_total{service="fx-rates",grpc_code=~"Unavailable|Internal|DeadlineExceeded|Unknown|DataLoss"}[5m])) / sum by (service) (rate(grpc_server_handled_total{service="fx-rates"}[5m])) > 0.02
    for: "10m"
    labels: {severity: page, team: ledger}
    annotations:
      summary: "{{ $labels.service }} is failing {{ $value | humanizePercentage }} of requests"
      runbook_url: https://runbooks.numerapay.example/alerts/FxRatesHighErrorRatio
- name: statements-export
  rules:
  - alert: StatementsExportLate
    expr: time() - max by (service) (export_last_success_timestamp_seconds{service="statements-export"}) > 3 * 3600
    for: "30m"
    labels: {severity: page, team: ledger}
    annotations:
      summary: "{{ $labels.service }} hasn't finished an export in over 3 hours"
      runbook_url: https://runbooks.numerapay.example/alerts/StatementsExportLate
AF_EOF

	#!/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
	smtp_smarthost: smtp.numerapay.example:587
	smtp_from: alertmanager@numerapay.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:
	- 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="risk"
	receiver: slack-risk
	routes:
	- matchers:
	- severity=~"page\|critical"
	receiver: pagerduty-risk
	continue: true
	- matchers:
	- severity="ticket"
	receiver: jira-risk
	continue: true
	- receiver: slack-risk
	# cards: still on the old match syntax
	- match:
	team: cards
	receiver: slack-cards
	routes:
	- match_re:
	severity: page\|critical
	receiver: pagerduty-cards
	continue: true
	- match:
	severity: ticket
	receiver: jira-cards
	continue: true
	- receiver: slack-cards
	- 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="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
	# ledger services from before team labels were everywhere
	- matchers:
	- service=~"ledger-api\|statements-export"
	receiver: slack-ledger
	routes:
	- matchers:
	- severity=~"page\|critical"
	receiver: pagerduty-ledger
	continue: true
	- receiver: slack-ledger
	- 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
	# teams below route alerts from the platform and data Prometheus servers
	- matchers:
	- team="edge"
	receiver: slack-edge
	group_interval: 10m
	routes:
	- matchers:
	- severity=~"page\|critical"
	receiver: pagerduty-edge
	continue: true
	- matchers:
	- severity="ticket"
	receiver: jira-edge
	continue: true
	- receiver: slack-edge
	# database-reliability wanted tickets in Slack as well as Jira (PLAT-1728)
	- 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="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="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
	- matchers:
	- team="messaging"
	receiver: slack-messaging
	routes:
	- matchers:
	- severity=~"page\|critical"
	receiver: pagerduty-messaging
	continue: true
	- matchers:
	- severity="ticket"
	receiver: jira-messaging
	continue: true
	# tickets and warnings per pod in Slack, so the channel shows which pod; pages group per service above
	- receiver: slack-messaging
	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
	# build-infra asked for hourly repeats while something is still firing
	- 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
	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.numerapay.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.numerapay.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.numerapay.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.numerapay.example/hooks/edge
	- 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.numerapay.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.numerapay.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.numerapay.example/hooks/ml_platform
	- 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.numerapay.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.numerapay.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.numerapay.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.numerapay.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.numerapay.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.numerapay.example/hooks/storage
	- 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.numerapay.example/hooks/treasury
	# unused since 2024, the SMTP relay it points at is gone
	- name: email-oncall
	email_configs:
	- to: oncall@numerapay.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="LedgerApiDown"
	target_matchers:
	- alertname=~"LedgerApiErrorBudgetBurnFast\|LedgerApiErrorBudgetBurnSlow\|LedgerApiHighErrorRatio"
	equal: [service]
	AF_EOF
	mkdir -p 'rules'
	cat > 'rules/cards-rules.yaml' <<'AF_EOF'
	apiVersion: monitoring.coreos.com/v1
	kind: PrometheusRule
	metadata:
	name: cards-rules
	namespace: monitoring
	labels:
	role: alert-rules
	spec:
	groups:
	- name: card-auth
	rules:
	- alert: CardAuthDown
	expr: \|
	sum by (service) (up{service="card-auth"}) == 0
	or absent(up{service="card-auth"})
	for: 1m
	labels:
	severity: page
	team: cards
	annotations:
	summary: card-auth has no healthy scrape targets
	runbook_url: https://runbooks.numerapay.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.05
	for: 10m
	labels:
	severity: page
	team: cards
	annotations:
	summary: "{{ $labels.service }} is failing {{ $value \| humanizePercentage }} of requests"
	runbook_url: https://runbooks.numerapay.example/alerts/CardAuthHighErrorRatio
	- alert: CardAuthTrafficBelowFloor
	expr: \|
	sum by (service) (rate(http_requests_total{service="card-auth"}[5m])) < 5
	and on (service) sum by (service) (up{service="card-auth"}) > 0
	for: 5m
	labels:
	severity: page
	team: cards
	annotations:
	summary: "{{ $labels.service }} is serving under its traffic floor with its pods up"
	runbook_url: https://runbooks.numerapay.example/alerts/CardAuthTrafficBelowFloor
	- alert: CardAuthErrorBudgetBurnFast
	expr: \|
	slo:sli_error:ratio_rate1h{service="card-auth"} > (14.4 * 0.005)
	and slo:sli_error:ratio_rate5m{service="card-auth"} > (14.4 * 0.005)
	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.numerapay.example/alerts/CardAuthErrorBudgetBurnFast
	- alert: CardAuthErrorBudgetBurnSlow
	expr: \|
	slo:sli_error:ratio_rate6h{service="card-auth"} > (6 * 0.005)
	and slo:sli_error:ratio_rate30m{service="card-auth"} > (6 * 0.005)
	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.numerapay.example/alerts/CardAuthErrorBudgetBurnSlow
	- name: card-worker
	rules:
	- alert: CardWorkerDown
	expr: \|
	sum by (service) (up{service="card-worker"}) == 0
	or absent(up{service="card-worker"})
	for: 1m
	labels:
	severity: page
	team: cards
	annotations:
	summary: card-worker has no healthy scrape targets
	runbook_url: https://runbooks.numerapay.example/alerts/CardWorkerDown
	# 5xx only; 429s are the rate limiter doing its job
	- alert: CardWorkerHighErrorRatio
	expr: \|
	sum by (service) (rate(http_requests_total{service="card-worker",code=~"5.."}[5m]))
	/ sum by (service) (rate(http_requests_total{service="card-worker"}[5m])) > 0.05
	for: 10m
	labels:
	severity: page
	team: cards
	annotations:
	summary: "{{ $labels.service }} is failing {{ $value \| humanizePercentage }} of requests"
	runbook_url: https://runbooks.numerapay.example/alerts/CardWorkerHighErrorRatio
	# average over the targets: half of them gone is a ticket even while the rest carry the load
	- alert: CardWorkerTargetsHalfDown
	expr: \|
	avg by (service) (up{service="card-worker"}) < 0.5
	and on (service) count by (service) (up{service="card-worker"}) >= 2
	for: 10m
	labels:
	severity: ticket
	team: cards
	annotations:
	summary: "{{ $labels.service }} has lost half of its targets"
	runbook_url: https://runbooks.numerapay.example/alerts/CardWorkerTargetsHalfDown
	AF_EOF
	mkdir -p 'rules'
	cat > 'rules/legacy-ledger.yml' <<'AF_EOF'
	# ledger 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: ledger-records
	rules:
	- record: job:grpc_calls:rate5m
	expr: sum by (job, service) (rate(grpc_server_handled_total{service="fx-rates"}[5m]))
	- record: job:grpc_errors:rate5m
	expr: sum by (job, service) (rate(grpc_server_handled_total{service="fx-rates",grpc_code=~"Unavailable\|Internal\|DeadlineExceeded\|Unknown\|DataLoss"}[5m]))
	- record: job:http_requests:rate5m
	expr: sum by (job, service) (rate(http_requests_total{service="ledger-api"}[5m]))
	- record: job:http_errors:rate5m
	expr: sum by (job, service) (rate(http_requests_total{service="ledger-api",code=~"5.."}[5m]))
	- name: ledger-api
	rules:
	# threshold agreed with ledger in PLAT-1677
	- alert: LedgerApiHighErrorRatio
	expr: sum by (service) (rate(http_requests_total{service="ledger-api",code=~"5.."}[5m])) / sum by (service) (rate(http_requests_total{service="ledger-api"}[5m])) > 0.02
	for: "10m"
	labels: {severity: page, team: ledger}
	annotations:
	summary: "{{ $labels.service }} is failing {{ $value \| humanizePercentage }} of requests"
	runbook_url: https://runbooks.numerapay.example/alerts/LedgerApiHighErrorRatio
	- alert: LedgerApiLatencyHigh
	expr: histogram_quantile(0.99, sum by (service, le) (rate(http_request_duration_seconds_bucket{service="ledger-api"}[5m]))) > 0.5
	for: "10m"
	labels: {severity: warning, team: ledger}
	annotations:
	summary: "{{ $labels.service }} p99 above 500ms"
	runbook_url: https://runbooks.numerapay.example/alerts/LedgerApiLatencyHigh
	- alert: LedgerApiLatencyHigh
	expr: histogram_quantile(0.99, sum by (service, le) (rate(http_request_duration_seconds_bucket{service="ledger-api"}[5m]))) > 1
	for: "10m"
	labels: {severity: critical, team: ledger}
	annotations:
	summary: "{{ $labels.service }} p99 above 1s"
	runbook_url: https://runbooks.numerapay.example/alerts/LedgerApiLatencyHigh
	- name: fx-rates
	rules:
	- alert: FxRatesHighErrorRatio
	expr: sum by (service) (rate(grpc_server_handled_total{service="fx-rates",grpc_code=~"Unavailable\|Internal\|DeadlineExceeded\|Unknown\|DataLoss"}[5m])) / sum by (service) (rate(grpc_server_handled_total{service="fx-rates"}[5m])) > 0.02
	for: "10m"
	labels: {severity: page, team: ledger}
	annotations:
	summary: "{{ $labels.service }} is failing {{ $value \| humanizePercentage }} of requests"
	runbook_url: https://runbooks.numerapay.example/alerts/FxRatesHighErrorRatio
	- name: statements-export
	rules:
	- alert: StatementsExportLate
	expr: time() - max by (service) (export_last_success_timestamp_seconds{service="statements-export"}) > 3 * 3600
	for: "30m"
	labels: {severity: page, team: ledger}
	annotations:
	summary: "{{ $labels.service }} hasn't finished an export in over 3 hours"
	runbook_url: https://runbooks.numerapay.example/alerts/StatementsExportLate
	AF_EOF