Datasets:

openenvforge
/

3ambench

#!/bin/bash
# oracle: rewrites changed files to the oracle state
set -euo pipefail
cd /workspace/monitoring
mkdir -p 'alertmanager'
cat > 'alertmanager/alertmanager.yml' <<'AF_EOF'
# Shared Alertmanager config (this repo, platform and data Prometheus servers).
# Receivers belong to the teams; ask before touching someone else's.
global:
  resolve_timeout: 5m
  slack_api_url_file: /etc/alertmanager/secrets/slack-url
templates:
- /etc/alertmanager/templates/*.tmpl
route:
  receiver: slack-alerts-default
  group_by: [alertname, service]
  group_wait: 30s
  group_interval: 5m
  repeat_interval: 4h
  routes:
  # rule evaluation problems. Nobody pages on these (yet).
  - matchers:
    - alertname=~"PrometheusRuleFailures|PrometheusRuleEvaluationSlow"
    receiver: slack-prometheus-meta
  # SRE sees every page as FYI; owners get paged by their own subtree below.
  - matchers:
    - severity=~"page|critical"
    receiver: slack-sre-fyi
    continue: true
  - matchers:
    - team="inventory"
    receiver: slack-inventory
    routes:
    - matchers:
      - severity=~"page|critical"
      receiver: pagerduty-inventory
      continue: true
    - matchers:
      - severity="ticket"
      receiver: jira-inventory
      continue: true
    - receiver: slack-inventory
  # loyalty: still on the old match syntax
  - match:
      team: loyalty
    receiver: slack-loyalty
    routes:
    - match_re:
        severity: page|critical
      receiver: pagerduty-loyalty
      continue: true
    - match:
        severity: ticket
      receiver: jira-loyalty
      continue: true
    - receiver: slack-loyalty
  - matchers:
    - team="booking"
    receiver: slack-booking-oncall
    routes:
    - matchers:
      - severity=~"page|critical"
      receiver: pagerduty-booking
      continue: true
    - matchers:
      - severity="ticket"
      receiver: jira-booking
      continue: true
    - receiver: slack-booking-oncall
  - matchers:
    - team="shopping"
    receiver: slack-shopping
    routes:
    - matchers:
      - severity=~"page|critical"
      receiver: pagerduty-shopping
      continue: true
    - matchers:
      - severity="ticket"
      receiver: jira-shopping
      continue: true
    - receiver: slack-shopping
  # shopping services from before team labels were everywhere
  - matchers:
    - service=~"fare-quotes|search-reindexer"
    receiver: slack-shopping
    routes:
    - matchers:
      - severity=~"page|critical"
      receiver: pagerduty-shopping
      continue: true
    - receiver: slack-shopping
  - matchers:
    - team="partner-feeds"
    receiver: slack-partner-feeds
    routes:
    - matchers:
      - severity=~"page|critical"
      receiver: pagerduty-partner-feeds
      continue: true
    - matchers:
      - severity="ticket"
      receiver: jira-partner-feeds
      continue: true
    - receiver: slack-partner-feeds
  # teams below route alerts from the platform and data Prometheus servers
  - 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="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="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
  # data-platform: fewer updates per group, too chatty at 5m
  - matchers:
    - team="data-platform"
    receiver: slack-data-platform
    group_interval: 10m
    routes:
    - matchers:
      - severity=~"page|critical"
      receiver: pagerduty-data-platform
      continue: true
    - matchers:
      - severity="ticket"
      receiver: jira-data-platform
      continue: true
    - receiver: slack-data-platform
  # database-reliability wanted tickets in Slack as well as Jira (SRE-2457)
  - 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="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="ml-platform"
    receiver: slack-ml-platform
    routes:
    - matchers:
      - severity=~"page|critical"
      receiver: pagerduty-ml-platform
      continue: true
    - matchers:
      - severity="ticket"
      receiver: jira-ml-platform
      continue: true
    - receiver: slack-ml-platform
  - matchers:
    - team="build-infra"
    receiver: slack-build-infra
    routes:
    - matchers:
      - severity=~"page|critical"
      receiver: pagerduty-build-infra
      continue: true
    - matchers:
      - severity="ticket"
      receiver: jira-build-infra
      continue: true
    # tickets and warnings per pod in Slack, so the channel shows which pod; pages group per service above
    - receiver: slack-build-infra
      group_by: [alertname, pod, service]
  - 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
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-booking
  pagerduty_configs:
  - routing_key_file: /etc/alertmanager/secrets/pagerduty/booking
- name: slack-booking
  slack_configs:
  - channel: "#booking-alerts"
    send_resolved: true
- name: jira-booking
  webhook_configs:
  - url: https://jira-bridge.int.kaafila.example/hooks/booking
- 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.kaafila.example/hooks/build_infra
- 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.kaafila.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.kaafila.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.int.kaafila.example/hooks/edge
- name: pagerduty-inventory
  pagerduty_configs:
  - routing_key_file: /etc/alertmanager/secrets/pagerduty/inventory
- name: slack-inventory
  slack_configs:
  - channel: "#inventory-alerts"
    send_resolved: true
- name: jira-inventory
  webhook_configs:
  - url: https://jira-bridge.int.kaafila.example/hooks/inventory
- name: pagerduty-loyalty
  pagerduty_configs:
  - routing_key_file: /etc/alertmanager/secrets/pagerduty/loyalty
- name: slack-loyalty
  slack_configs:
  - channel: "#loyalty-alerts"
    send_resolved: true
- name: jira-loyalty
  webhook_configs:
  - url: https://jira-bridge.int.kaafila.example/hooks/loyalty
- 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.kaafila.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.kaafila.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.kaafila.example/hooks/network
- name: pagerduty-partner-feeds
  pagerduty_configs:
  - routing_key_file: /etc/alertmanager/secrets/pagerduty/partner-feeds
- name: slack-partner-feeds
  slack_configs:
  - channel: "#partner-feeds-alerts"
    send_resolved: true
- name: jira-partner-feeds
  webhook_configs:
  - url: https://jira-bridge.int.kaafila.example/hooks/partner_feeds
- 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.kaafila.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.int.kaafila.example/hooks/security_ops
- name: pagerduty-shopping
  pagerduty_configs:
  - routing_key_file: /etc/alertmanager/secrets/pagerduty/shopping
- name: slack-shopping
  slack_configs:
  - channel: "#shopping-alerts"
    send_resolved: true
- name: jira-shopping
  webhook_configs:
  - url: https://jira-bridge.int.kaafila.example/hooks/shopping
# nothing routes here since the rota moved to PagerDuty; ask before deleting
- name: slack-old-oncall
  slack_configs:
  - channel: "#oncall-old"
    send_resolved: true
- name: slack-booking-oncall
  slack_configs:
  - channel: "#booking-oncall"
    send_resolved: true
inhibit_rules:
# a critical copy holds back the warning copy of the same alert
- source_matchers:
  - severity="critical"
  target_matchers:
  - severity="warning"
  equal: [alertname, service]
AF_EOF
mkdir -p 'rules'
cat > 'rules/capacity.yml' <<'AF_EOF'
# Capacity tickets. Pages for crashes come from the platform Prometheus.
groups:
- name: capacity
  rules:
  - alert: ContainerMemoryNearLimit
    expr: |
      max by (service) (container_memory_working_set_bytes{service="inventory-sync",container="inventory-sync"} / container_spec_memory_limit_bytes{service="inventory-sync",container="inventory-sync"}) > 0.9
    for: 15m
    labels:
      severity: ticket
      team: inventory
    annotations:
      summary: "{{ $labels.service }} keeps running close to its memory limit"
      runbook_url: https://runbooks.int.kaafila.example/alerts/ContainerMemoryNearLimit
  - alert: ContainerMemoryNearLimit
    expr: |
      max by (service) (container_memory_working_set_bytes{service="hotel-indexer",container="hotel-indexer"} / container_spec_memory_limit_bytes{service="hotel-indexer",container="hotel-indexer"}) > 0.9
    for: 15m
    labels:
      severity: ticket
      team: partner-feeds
    annotations:
      summary: "{{ $labels.service }} keeps running close to its memory limit"
      runbook_url: https://runbooks.int.kaafila.example/alerts/ContainerMemoryNearLimit
  - alert: ContainerMemoryNearLimit
    expr: |
      max by (service) (container_memory_working_set_bytes{service="booking-worker",container="booking-worker"} / container_spec_memory_limit_bytes{service="booking-worker",container="booking-worker"}) > 0.9
    for: 15m
    labels:
      severity: ticket
      team: booking
    annotations:
      summary: "{{ $labels.service }} keeps running close to its memory limit"
      runbook_url: https://runbooks.int.kaafila.example/alerts/ContainerMemoryNearLimit
AF_EOF
mkdir -p 'rules'
cat > 'rules/legacy-booking.yml' <<'AF_EOF'
# booking 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: booking-records
  rules:
  - record: job:http_requests:rate5m
    expr: sum by (job, service) (rate(http_requests_total{service=~"booking-api|pnr-worker|booking-worker"}[5m]))
  - record: job:http_errors:rate5m
    expr: sum by (job, service) (rate(http_requests_total{service=~"booking-api|pnr-worker|booking-worker",code=~"5.."}[5m]))
- name: booking-api
  rules:
  - alert: BookingApiHighErrorRatio
    expr: sum by (service) (rate(http_requests_total{service="booking-api",code=~"5.."}[5m])) / sum by (service) (rate(http_requests_total{service="booking-api"}[5m])) > 0.02
    for: "10m"
    labels: {severity: page, team: booking}
    annotations:
      summary: "{{ $labels.service }} is failing {{ $value | humanizePercentage }} of requests"
      runbook_url: https://runbooks.int.kaafila.example/alerts/BookingApiHighErrorRatio
  - alert: BookingApiLatencyHigh
    expr: histogram_quantile(0.99, sum by (service, le) (rate(http_request_duration_seconds_bucket{service="booking-api"}[5m]))) > 0.5
    for: "10m"
    labels: {severity: warning, team: booking}
    annotations:
      summary: "{{ $labels.service }} p99 above 500ms"
      runbook_url: https://runbooks.int.kaafila.example/alerts/BookingApiLatencyHigh
  - alert: BookingApiLatencyHigh
    expr: histogram_quantile(0.99, sum by (service, le) (rate(http_request_duration_seconds_bucket{service="booking-api"}[5m]))) > 1
    for: "10m"
    labels: {severity: critical, team: booking}
    annotations:
      summary: "{{ $labels.service }} p99 above 1s"
      runbook_url: https://runbooks.int.kaafila.example/alerts/BookingApiLatencyHigh
- name: pnr-worker
  rules:
  # threshold agreed with booking in SRE-1604
  - alert: PnrWorkerHighErrorRatio
    expr: sum by (service) (rate(http_requests_total{service="pnr-worker",code=~"5.."}[5m])) / sum by (service) (rate(http_requests_total{service="pnr-worker"}[5m])) > 0.1
    for: "10m"
    labels: {severity: page, team: booking}
    annotations:
      summary: "{{ $labels.service }} is failing {{ $value | humanizePercentage }} of requests"
      runbook_url: https://runbooks.int.kaafila.example/alerts/PnrWorkerHighErrorRatio
  - alert: PnrWorkerDbConnectionsHigh
    expr: max by (service) (db_pool_connections_active{service="pnr-worker"} / db_pool_connections_max{service="pnr-worker"}) > 0.8
    for: "5m"
    labels: {severity: warning, team: booking}
    annotations:
      summary: "{{ $labels.service }} is using over 80% of its DB pool"
      runbook_url: https://runbooks.int.kaafila.example/alerts/PnrWorkerDbConnectionsHigh
  - alert: PnrWorkerDbConnectionsHigh
    expr: max by (service) (db_pool_connections_active{service="pnr-worker"} / db_pool_connections_max{service="pnr-worker"}) > 0.95
    for: "5m"
    labels: {severity: critical, team: booking}
    annotations:
      summary: "{{ $labels.service }} DB pool nearly exhausted"
      runbook_url: https://runbooks.int.kaafila.example/alerts/PnrWorkerDbConnectionsHigh
  # average the pods: they all run with the same limit, so the mean is what we size it by
  - alert: PnrWorkerCpuThrottled
    expr: avg by (service) (rate(container_cpu_cfs_throttled_periods_total{service="pnr-worker",container="pnr-worker"}[5m]) / rate(container_cpu_cfs_periods_total{service="pnr-worker",container="pnr-worker"}[5m])) > 0.25
    for: "30m"
    labels: {severity: ticket, team: booking}
    annotations:
      summary: "{{ $labels.service }} pods spend over a quarter of their CPU periods throttled"
      runbook_url: https://runbooks.int.kaafila.example/alerts/PnrWorkerCpuThrottled
- name: booking-worker
  rules:
  # threshold agreed with booking in SRE-1653
  - alert: BookingWorkerHighErrorRatio
    expr: sum by (service) (rate(http_requests_total{service="booking-worker",code=~"5.."}[5m])) / sum by (service) (rate(http_requests_total{service="booking-worker"}[5m])) > 0.02
    for: "10m"
    labels: {severity: page, team: booking}
    annotations:
      summary: "{{ $labels.service }} is failing {{ $value | humanizePercentage }} of requests"
      runbook_url: https://runbooks.int.kaafila.example/alerts/BookingWorkerHighErrorRatio
  - alert: BookingWorkerDbConnectionsHigh
    expr: max by (service) (db_pool_connections_active{service="booking-worker"} / db_pool_connections_max{service="booking-worker"}) > 0.8
    for: "5m"
    labels: {severity: warning, team: booking}
    annotations:
      summary: "{{ $labels.service }} is using over 80% of its DB pool"
      runbook_url: https://runbooks.int.kaafila.example/alerts/BookingWorkerDbConnectionsHigh
  - alert: BookingWorkerDbConnectionsHigh
    expr: max by (service) (db_pool_connections_active{service="booking-worker"} / db_pool_connections_max{service="booking-worker"}) > 0.95
    for: "5m"
    labels: {severity: critical, team: booking}
    annotations:
      summary: "{{ $labels.service }} DB pool nearly exhausted"
      runbook_url: https://runbooks.int.kaafila.example/alerts/BookingWorkerDbConnectionsHigh
AF_EOF
mkdir -p 'rules'
cat > 'rules/legacy-shopping.yml' <<'AF_EOF'
# shopping 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: shopping-records
  rules:
  - record: job:http_requests:rate5m
    expr: sum by (job, service) (rate(http_requests_total{service="fare-quotes"}[5m]))
  - record: job:http_errors:rate5m
    expr: sum by (job, service) (rate(http_requests_total{service="fare-quotes",code=~"5.."}[5m]))
- name: fare-quotes
  rules:
  # 5% from SRE-1225; callers retry fare-quotes, a few errors never reach a user
  - alert: FareQuotesHighErrorRatio
    expr: sum by (service) (rate(http_requests_total{service="fare-quotes",code=~"5.."}[5m])) / sum by (service) (rate(http_requests_total{service="fare-quotes"}[5m])) > 0.05
    for: "10m"
    labels: {severity: page, team: shopping}
    annotations:
      summary: "{{ $labels.service }} is failing {{ $value | humanizePercentage }} of requests"
      runbook_url: https://runbooks.int.kaafila.example/alerts/FareQuotesHighErrorRatio
  - alert: FareQuotesLatencyHigh
    expr: histogram_quantile(0.99, sum by (service, le) (rate(http_request_duration_seconds_bucket{service="fare-quotes"}[5m]))) > 0.5
    for: "10m"
    labels: {severity: warning, team: shopping}
    annotations:
      summary: "{{ $labels.service }} p99 above 500ms"
      runbook_url: https://runbooks.int.kaafila.example/alerts/FareQuotesLatencyHigh
  # 1s: past this the gateway starts timing callers out
  - alert: FareQuotesLatencyHigh
    expr: histogram_quantile(0.99, sum by (service, le) (rate(http_request_duration_seconds_bucket{service="fare-quotes"}[5m]))) > 1
    for: "10m"
    labels: {severity: critical, team: shopping}
    annotations:
      summary: "{{ $labels.service }} p99 above 1s"
      runbook_url: https://runbooks.int.kaafila.example/alerts/FareQuotesLatencyHigh
  - alert: FareQuotesDbConnectionsHigh
    expr: max by (service) (db_pool_connections_active{service="fare-quotes"} / db_pool_connections_max{service="fare-quotes"}) > 0.8
    for: "5m"
    labels: {severity: warning, team: shopping}
    annotations:
      summary: "{{ $labels.service }} is using over 80% of its DB pool"
      runbook_url: https://runbooks.int.kaafila.example/alerts/FareQuotesDbConnectionsHigh
  - alert: FareQuotesDbConnectionsHigh
    expr: max by (service) (db_pool_connections_active{service="fare-quotes"} / db_pool_connections_max{service="fare-quotes"}) > 0.95
    for: "5m"
    labels: {severity: critical, team: shopping}
    annotations:
      summary: "{{ $labels.service }} DB pool nearly exhausted"
      runbook_url: https://runbooks.int.kaafila.example/alerts/FareQuotesDbConnectionsHigh
  - alert: ReplicationLagHigh
    expr: max by (service) (pg_replication_lag_seconds{service="fare-quotes"}) > 30
    for: "10m"
    labels: {severity: page, team: shopping}
    annotations:
      summary: "{{ $labels.service }} replica is behind the primary"
      description: Replication lag is {{ $value | humanize }}s.
      runbook_url: https://runbooks.int.kaafila.example/alerts/ReplicationLagHigh
- name: search-reindexer
  rules:
  - alert: SearchReindexerExportLate
    expr: time() - max by (service) (export_last_success_timestamp_seconds{service="search-reindexer"}) > 3 * 3600
    for: "30m"
    labels: {severity: ticket, team: shopping}
    annotations:
      summary: "{{ $labels.service }} hasn't finished an export in over 3 hours"
      runbook_url: https://runbooks.int.kaafila.example/alerts/SearchReindexerExportLate
AF_EOF
mkdir -p 'rules'
cat > 'rules/loyalty-rules.yaml' <<'AF_EOF'
apiVersion: monitoring.coreos.com/v1
kind: PrometheusRule
metadata:
  name: loyalty-rules
  namespace: monitoring
  labels:
    role: alert-rules
spec:
  groups:
  - name: loyalty-points
    rules:
    - alert: LoyaltyPointsDown
      expr: |
        sum by (service) (up{service="loyalty-points"}) == 0
        or absent(up{service="loyalty-points"})
      for: 3m
      labels:
        severity: page
        team: loyalty
      annotations:
        summary: loyalty-points has no healthy scrape targets
        runbook_url: https://runbooks.int.kaafila.example/alerts/LoyaltyPointsDown
    - alert: LoyaltyPointsHighErrorRatio
      expr: |
        sum by (service) (rate(http_requests_total{service="loyalty-points",code=~"5.."}[5m]))
        / sum by (service) (rate(http_requests_total{service="loyalty-points"}[5m])) > 0.02
      for: 10m
      labels:
        severity: page
        team: loyalty
      annotations:
        summary: "{{ $labels.service }} is failing {{ $value | humanizePercentage }} of requests"
        runbook_url: https://runbooks.int.kaafila.example/alerts/LoyaltyPointsHighErrorRatio
    - alert: LoyaltyPointsErrorBudgetBurnFast
      expr: |
        slo:sli_error:ratio_rate1h{service="loyalty-points"} > (3.36 * 0.01)
        and slo:sli_error:ratio_rate5m{service="loyalty-points"} > (3.36 * 0.01)
      for: 2m
      labels:
        severity: page
        team: loyalty
        slo: loyalty-points-availability
      annotations:
        summary: "{{ $labels.service }} is spending its error budget fast"
        runbook_url: https://runbooks.int.kaafila.example/alerts/LoyaltyPointsErrorBudgetBurnFast
    - alert: LoyaltyPointsErrorBudgetBurnSlow
      expr: |
        slo:sli_error:ratio_rate6h{service="loyalty-points"} > (1.4 * 0.01)
        and slo:sli_error:ratio_rate30m{service="loyalty-points"} > (1.4 * 0.01)
      for: 15m
      labels:
        severity: ticket
        team: loyalty
        slo: loyalty-points-availability
      annotations:
        summary: "{{ $labels.service }} is spending its error budget steadily"
        runbook_url: https://runbooks.int.kaafila.example/alerts/LoyaltyPointsErrorBudgetBurnSlow
  - name: seatmap-svc
    rules:
    - alert: SeatmapSvcDown
      expr: |
        sum by (service) (up{service="seatmap-svc"}) == 0
        or absent(up{service="seatmap-svc"})
      for: 3m
      labels:
        severity: page
        team: loyalty
      annotations:
        summary: seatmap-svc has no healthy scrape targets
        runbook_url: https://runbooks.int.kaafila.example/alerts/SeatmapSvcDown
    # 2% from SRE-2814; callers retry seatmap-svc, a few errors never reach a user
    - alert: SeatmapSvcHighErrorRatio
      expr: |
        sum by (service) (rate(grpc_server_handled_total{service="seatmap-svc",grpc_code=~"Unavailable|Internal|DeadlineExceeded|Unknown|DataLoss"}[5m]))
        / sum by (service) (rate(grpc_server_handled_total{service="seatmap-svc"}[5m])) > 0.02
      for: 10m
      labels:
        severity: page
        team: loyalty
      annotations:
        summary: "{{ $labels.service }} is failing {{ $value | humanizePercentage }} of requests"
        runbook_url: https://runbooks.int.kaafila.example/alerts/SeatmapSvcHighErrorRatio
    - alert: SeatmapSvcErrorBudgetBurnFast
      expr: |
        slo:sli_error:ratio_rate1h{service="seatmap-svc"} > (14.4 * 0.005)
        and slo:sli_error:ratio_rate5m{service="seatmap-svc"} > (14.4 * 0.005)
      for: 2m
      labels:
        severity: page
        team: loyalty
        slo: seatmap-svc-availability
      annotations:
        summary: "{{ $labels.service }} is spending its error budget fast"
        runbook_url: https://runbooks.int.kaafila.example/alerts/SeatmapSvcErrorBudgetBurnFast
    - alert: SeatmapSvcErrorBudgetBurnSlow
      expr: |
        slo:sli_error:ratio_rate6h{service="seatmap-svc"} > (6 * 0.005)
        and slo:sli_error:ratio_rate30m{service="seatmap-svc"} > (6 * 0.005)
      for: 15m
      labels:
        severity: ticket
        team: loyalty
        slo: seatmap-svc-availability
      annotations:
        summary: "{{ $labels.service }} is spending its error budget steadily"
        runbook_url: https://runbooks.int.kaafila.example/alerts/SeatmapSvcErrorBudgetBurnSlow
AF_EOF
mkdir -p 'rules'
cat > 'rules/service-health.yml' <<'AF_EOF'
# One Down alert per service. See README, Service health.
groups:
- name: service-health
  rules:
  - alert: BookingApiDown
    expr: |
      sum by (service) (up{service="booking-api"}) == 0
      or absent(up{service="booking-api"})
    for: 3m
    labels:
      severity: page
      team: booking
    annotations:
      summary: booking-api has no healthy scrape targets
      runbook_url: https://runbooks.int.kaafila.example/alerts/BookingApiDown
  - alert: FareQuotesDown
    expr: |
      sum by (service) (up{service="fare-quotes"}) == 0
      or absent(up{service="fare-quotes"})
    for: 3m
    labels:
      severity: page
      team: shopping
    annotations:
      summary: fare-quotes has no healthy scrape targets
      runbook_url: https://runbooks.int.kaafila.example/alerts/FareQuotesDown
  # absent() too: inventory-sync was scaled to zero by mistake once and the sum just went away
  - alert: InventorySyncDown
    expr: |
      sum by (service) (up{service="inventory-sync"}) == 0
      or absent(up{service="inventory-sync"})
    for: 3m
    labels:
      severity: page
      team: inventory
    annotations:
      summary: inventory-sync has no healthy scrape targets
      runbook_url: https://runbooks.int.kaafila.example/alerts/InventorySyncDown
  - alert: PnrWorkerDown
    expr: |
      sum by (service) (up{service="pnr-worker"}) == 0
      or absent(up{service="pnr-worker"})
    for: 3m
    labels:
      severity: page
      team: booking
    annotations:
      summary: pnr-worker has no healthy scrape targets
      runbook_url: https://runbooks.int.kaafila.example/alerts/PnrWorkerDown
  - alert: SearchReindexerDown
    expr: |
      sum by (service) (up{service="search-reindexer"}) == 0
      or absent(up{service="search-reindexer"})
    for: 3m
    labels:
      severity: page
      team: shopping
    annotations:
      summary: search-reindexer has no healthy scrape targets
      runbook_url: https://runbooks.int.kaafila.example/alerts/SearchReindexerDown
  - alert: HotelIndexerDown
    expr: |
      sum by (service) (up{service="hotel-indexer"}) == 0
      or absent(up{service="hotel-indexer"})
    for: 3m
    labels:
      severity: page
      team: partner-feeds
    annotations:
      summary: hotel-indexer has no healthy scrape targets
      runbook_url: https://runbooks.int.kaafila.example/alerts/HotelIndexerDown
  - alert: BookingWorkerDown
    expr: |
      sum by (service) (up{service="booking-worker"}) == 0
      or absent(up{service="booking-worker"})
    for: 3m
    labels:
      severity: page
      team: booking
    annotations:
      summary: booking-worker has no healthy scrape targets
      runbook_url: https://runbooks.int.kaafila.example/alerts/BookingWorkerDown
AF_EOF