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.fernhop.example:587
  smtp_from: alertmanager@fernhop.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:
    - service="fare-quotes-legacy"
    receiver: slack-shopping
    routes:
    - matchers:
      - severity=~"page|critical"
      receiver: pagerduty-shopping
      continue: true
    - receiver: slack-shopping
  - 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
  - matchers:
    - team="loyalty"
    receiver: slack-loyalty
    routes:
    - matchers:
      - severity=~"page|critical"
      receiver: pagerduty-loyalty
      continue: true
    - matchers:
      - severity="ticket"
      receiver: jira-loyalty
      continue: true
    - receiver: slack-loyalty
  - matchers:
    - team="inventory"
    receiver: slack-inventory-oncall
    routes:
    - matchers:
      - severity=~"page|critical"
      receiver: pagerduty-inventory
      continue: true
    - matchers:
      - severity="ticket"
      receiver: jira-inventory
      continue: true
    - receiver: slack-inventory-oncall
  - matchers:
    - team="booking"
    receiver: slack-booking
    routes:
    - matchers:
      - severity=~"page|critical"
      receiver: pagerduty-booking
      continue: true
    - matchers:
      - severity="ticket"
      receiver: jira-booking
      continue: true
    - receiver: slack-booking
  # airport-ops: still on the old match syntax
  - match:
      team: airport-ops
    receiver: slack-airport-ops
    routes:
    - receiver: pagerduty-airport-ops
      continue: true
      match:
        severity: page|critical
    - match:
        severity: ticket
      receiver: jira-airport-ops
      continue: true
    - receiver: slack-airport-ops
  # shopping services from before team labels were everywhere
  - matchers:
    - service=~"fare-quotes|search-reindexer|hotel-indexer"
    receiver: slack-shopping
    routes:
    - matchers:
      - severity=~"page|critical"
      receiver: pagerduty-shopping
      continue: true
    - receiver: slack-shopping
  # teams below route alerts from the platform and data Prometheus servers
  - 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="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
  # data-platform asked for hourly repeats while something is still firing
  - matchers:
    - team="data-platform"
    receiver: slack-data-platform
    repeat_interval: 1h
    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="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="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
  # platform wanted tickets in Slack as well as Jira (PLAT-1269)
  - 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
  # build-infra: fewer updates per group, too chatty at 5m
  - matchers:
    - team="build-infra"
    receiver: slack-build-infra
    group_interval: 10m
    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="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
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-airport-ops
  pagerduty_configs:
  - routing_key_file: /etc/alertmanager/secrets/pagerduty/airport-ops
- name: slack-airport-ops
  slack_configs:
  - channel: "#airport-ops-alerts"
    send_resolved: true
- name: jira-airport-ops
  webhook_configs:
  - url: https://jira-bridge.fernhop.example/hooks/airport_ops
- 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.fernhop.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.fernhop.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.fernhop.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.fernhop.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.fernhop.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.fernhop.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.fernhop.example/hooks/loyalty
- 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.fernhop.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.fernhop.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.fernhop.example/hooks/platform
- 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.fernhop.example/hooks/shopping
- 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.fernhop.example/hooks/storage
# unused since 2024, the SMTP relay it points at is gone
- name: email-oncall
  email_configs:
  - to: oncall@fernhop.example
    send_resolved: false
- name: slack-inventory-oncall
  slack_configs:
  - channel: "#inventory-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="pnr-worker",container="pnr-worker"} / container_spec_memory_limit_bytes{service="pnr-worker",container="pnr-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.fernhop.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.fernhop.example/alerts/ContainerMemoryNearLimit
AF_EOF
mkdir -p 'rules'
cat > 'rules/legacy-inventory.yml' <<'AF_EOF'
# inventory 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: inventory-records
  rules:
  - record: job:http_requests:rate5m
    expr: sum by (job, service) (rate(http_requests_total{service="inventory-sync"}[5m]))
  - record: job:http_errors:rate5m
    expr: sum by (job, service) (rate(http_requests_total{service="inventory-sync",code=~"5.."}[5m]))
- name: inventory-sync
  rules:
  - alert: InventorySyncHighErrorRatio
    expr: sum by (service) (rate(http_requests_total{service="inventory-sync",code=~"5.."}[5m])) / sum by (service) (rate(http_requests_total{service="inventory-sync"}[5m])) > 0.1
    for: "10m"
    labels: {severity: page, team: inventory}
    annotations:
      summary: "{{ $labels.service }} is failing {{ $value | humanizePercentage }} of requests"
      runbook_url: https://runbooks.fernhop.example/alerts/InventorySyncHighErrorRatio
  # average over the targets: half of them gone is a ticket even while the rest carry the load
  - alert: InventorySyncTargetsHalfDown
    expr: avg by (service) (up{service="inventory-sync"}) < 0.5 and on (service) count by (service) (up{service="inventory-sync"}) >= 2
    for: "10m"
    labels: {severity: ticket, team: inventory}
    annotations:
      summary: "{{ $labels.service }} has lost half of its targets"
      runbook_url: https://runbooks.fernhop.example/alerts/InventorySyncTargetsHalfDown
AF_EOF
mkdir -p 'rules'
cat > 'rules/legacy-loyalty.yml' <<'AF_EOF'
# loyalty 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: loyalty-records
  rules:
  - record: job:http_requests:rate5m
    expr: sum by (job, service) (rate(http_requests_total{service="loyalty-points"}[5m]))
  - record: job:http_errors:rate5m
    expr: sum by (job, service) (rate(http_requests_total{service="loyalty-points",code=~"5.."}[5m]))
- name: loyalty-points
  rules:
  # threshold agreed with loyalty in PLAT-1277
  - 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.fernhop.example/alerts/LoyaltyPointsHighErrorRatio
  - alert: LoyaltyPointsLatencyHigh
    expr: histogram_quantile(0.99, sum by (service, le) (rate(http_request_duration_seconds_bucket{service="loyalty-points"}[5m]))) > 0.5
    for: "10m"
    labels: {severity: warning, team: loyalty}
    annotations:
      summary: "{{ $labels.service }} p99 above 500ms"
      runbook_url: https://runbooks.fernhop.example/alerts/LoyaltyPointsLatencyHigh
  - alert: LoyaltyPointsLatencyHigh
    expr: histogram_quantile(0.99, sum by (service, le) (rate(http_request_duration_seconds_bucket{service="loyalty-points"}[5m]))) > 1
    for: "10m"
    labels: {severity: critical, team: loyalty}
    annotations:
      summary: "{{ $labels.service }} p99 above 1s"
      runbook_url: https://runbooks.fernhop.example/alerts/LoyaltyPointsLatencyHigh
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: 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.fernhop.example/alerts/FareQuotesDown
  - 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.fernhop.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.fernhop.example/alerts/HotelIndexerDown
  - 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.fernhop.example/alerts/LoyaltyPointsDown
  - 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.fernhop.example/alerts/InventorySyncDown
AF_EOF
mkdir -p 'rules'
cat > 'rules/slo-loyalty-points.yml' <<'AF_EOF'
groups:
- name: slo-loyalty-points
  rules:
  - alert: LoyaltyPointsErrorBudgetBurnFast
    expr: |
      slo:sli_error:ratio_rate1h{service="loyalty-points"} > (14.4 * 0.005)
      and slo:sli_error:ratio_rate5m{service="loyalty-points"} > (14.4 * 0.005)
    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.fernhop.example/alerts/LoyaltyPointsErrorBudgetBurnFast
  - alert: LoyaltyPointsErrorBudgetBurnSlow
    expr: |
      slo:sli_error:ratio_rate6h{service="loyalty-points"} > (6 * 0.005)
      and slo:sli_error:ratio_rate30m{service="loyalty-points"} > (6 * 0.005)
    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.fernhop.example/alerts/LoyaltyPointsErrorBudgetBurnSlow
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.fernhop.example:587
	smtp_from: alertmanager@fernhop.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:
	- service="fare-quotes-legacy"
	receiver: slack-shopping
	routes:
	- matchers:
	- severity=~"page\|critical"
	receiver: pagerduty-shopping
	continue: true
	- receiver: slack-shopping
	- 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
	- matchers:
	- team="loyalty"
	receiver: slack-loyalty
	routes:
	- matchers:
	- severity=~"page\|critical"
	receiver: pagerduty-loyalty
	continue: true
	- matchers:
	- severity="ticket"
	receiver: jira-loyalty
	continue: true
	- receiver: slack-loyalty
	- matchers:
	- team="inventory"
	receiver: slack-inventory-oncall
	routes:
	- matchers:
	- severity=~"page\|critical"
	receiver: pagerduty-inventory
	continue: true
	- matchers:
	- severity="ticket"
	receiver: jira-inventory
	continue: true
	- receiver: slack-inventory-oncall
	- matchers:
	- team="booking"
	receiver: slack-booking
	routes:
	- matchers:
	- severity=~"page\|critical"
	receiver: pagerduty-booking
	continue: true
	- matchers:
	- severity="ticket"
	receiver: jira-booking
	continue: true
	- receiver: slack-booking
	# airport-ops: still on the old match syntax
	- match:
	team: airport-ops
	receiver: slack-airport-ops
	routes:
	- receiver: pagerduty-airport-ops
	continue: true
	match:
	severity: page\|critical
	- match:
	severity: ticket
	receiver: jira-airport-ops
	continue: true
	- receiver: slack-airport-ops
	# shopping services from before team labels were everywhere
	- matchers:
	- service=~"fare-quotes\|search-reindexer\|hotel-indexer"
	receiver: slack-shopping
	routes:
	- matchers:
	- severity=~"page\|critical"
	receiver: pagerduty-shopping
	continue: true
	- receiver: slack-shopping
	# teams below route alerts from the platform and data Prometheus servers
	- 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="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
	# data-platform asked for hourly repeats while something is still firing
	- matchers:
	- team="data-platform"
	receiver: slack-data-platform
	repeat_interval: 1h
	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="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="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
	# platform wanted tickets in Slack as well as Jira (PLAT-1269)
	- 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
	# build-infra: fewer updates per group, too chatty at 5m
	- matchers:
	- team="build-infra"
	receiver: slack-build-infra
	group_interval: 10m
	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="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
	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-airport-ops
	pagerduty_configs:
	- routing_key_file: /etc/alertmanager/secrets/pagerduty/airport-ops
	- name: slack-airport-ops
	slack_configs:
	- channel: "#airport-ops-alerts"
	send_resolved: true
	- name: jira-airport-ops
	webhook_configs:
	- url: https://jira-bridge.fernhop.example/hooks/airport_ops
	- 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.fernhop.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.fernhop.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.fernhop.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.fernhop.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.fernhop.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.fernhop.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.fernhop.example/hooks/loyalty
	- 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.fernhop.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.fernhop.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.fernhop.example/hooks/platform
	- 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.fernhop.example/hooks/shopping
	- 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.fernhop.example/hooks/storage
	# unused since 2024, the SMTP relay it points at is gone
	- name: email-oncall
	email_configs:
	- to: oncall@fernhop.example
	send_resolved: false
	- name: slack-inventory-oncall
	slack_configs:
	- channel: "#inventory-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="pnr-worker",container="pnr-worker"} / container_spec_memory_limit_bytes{service="pnr-worker",container="pnr-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.fernhop.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.fernhop.example/alerts/ContainerMemoryNearLimit
	AF_EOF
	mkdir -p 'rules'
	cat > 'rules/legacy-inventory.yml' <<'AF_EOF'
	# inventory 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: inventory-records
	rules:
	- record: job:http_requests:rate5m
	expr: sum by (job, service) (rate(http_requests_total{service="inventory-sync"}[5m]))
	- record: job:http_errors:rate5m
	expr: sum by (job, service) (rate(http_requests_total{service="inventory-sync",code=~"5.."}[5m]))
	- name: inventory-sync
	rules:
	- alert: InventorySyncHighErrorRatio
	expr: sum by (service) (rate(http_requests_total{service="inventory-sync",code=~"5.."}[5m])) / sum by (service) (rate(http_requests_total{service="inventory-sync"}[5m])) > 0.1
	for: "10m"
	labels: {severity: page, team: inventory}
	annotations:
	summary: "{{ $labels.service }} is failing {{ $value \| humanizePercentage }} of requests"
	runbook_url: https://runbooks.fernhop.example/alerts/InventorySyncHighErrorRatio
	# average over the targets: half of them gone is a ticket even while the rest carry the load
	- alert: InventorySyncTargetsHalfDown
	expr: avg by (service) (up{service="inventory-sync"}) < 0.5 and on (service) count by (service) (up{service="inventory-sync"}) >= 2
	for: "10m"
	labels: {severity: ticket, team: inventory}
	annotations:
	summary: "{{ $labels.service }} has lost half of its targets"
	runbook_url: https://runbooks.fernhop.example/alerts/InventorySyncTargetsHalfDown
	AF_EOF
	mkdir -p 'rules'
	cat > 'rules/legacy-loyalty.yml' <<'AF_EOF'
	# loyalty 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: loyalty-records
	rules:
	- record: job:http_requests:rate5m
	expr: sum by (job, service) (rate(http_requests_total{service="loyalty-points"}[5m]))
	- record: job:http_errors:rate5m
	expr: sum by (job, service) (rate(http_requests_total{service="loyalty-points",code=~"5.."}[5m]))
	- name: loyalty-points
	rules:
	# threshold agreed with loyalty in PLAT-1277
	- 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.fernhop.example/alerts/LoyaltyPointsHighErrorRatio
	- alert: LoyaltyPointsLatencyHigh
	expr: histogram_quantile(0.99, sum by (service, le) (rate(http_request_duration_seconds_bucket{service="loyalty-points"}[5m]))) > 0.5
	for: "10m"
	labels: {severity: warning, team: loyalty}
	annotations:
	summary: "{{ $labels.service }} p99 above 500ms"
	runbook_url: https://runbooks.fernhop.example/alerts/LoyaltyPointsLatencyHigh
	- alert: LoyaltyPointsLatencyHigh
	expr: histogram_quantile(0.99, sum by (service, le) (rate(http_request_duration_seconds_bucket{service="loyalty-points"}[5m]))) > 1
	for: "10m"
	labels: {severity: critical, team: loyalty}
	annotations:
	summary: "{{ $labels.service }} p99 above 1s"
	runbook_url: https://runbooks.fernhop.example/alerts/LoyaltyPointsLatencyHigh
	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: 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.fernhop.example/alerts/FareQuotesDown
	- 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.fernhop.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.fernhop.example/alerts/HotelIndexerDown
	- 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.fernhop.example/alerts/LoyaltyPointsDown
	- 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.fernhop.example/alerts/InventorySyncDown
	AF_EOF
	mkdir -p 'rules'
	cat > 'rules/slo-loyalty-points.yml' <<'AF_EOF'
	groups:
	- name: slo-loyalty-points
	rules:
	- alert: LoyaltyPointsErrorBudgetBurnFast
	expr: \|
	slo:sli_error:ratio_rate1h{service="loyalty-points"} > (14.4 * 0.005)
	and slo:sli_error:ratio_rate5m{service="loyalty-points"} > (14.4 * 0.005)
	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.fernhop.example/alerts/LoyaltyPointsErrorBudgetBurnFast
	- alert: LoyaltyPointsErrorBudgetBurnSlow
	expr: \|
	slo:sli_error:ratio_rate6h{service="loyalty-points"} > (6 * 0.005)
	and slo:sli_error:ratio_rate30m{service="loyalty-points"} > (6 * 0.005)
	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.fernhop.example/alerts/LoyaltyPointsErrorBudgetBurnSlow
	AF_EOF