#!/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
  smtp_smarthost: smtp.corp.cartohale.example:587
  smtp_from: alertmanager@corp.cartohale.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
  # pricing: still on the old match syntax
  - match:
      team: pricing
    receiver: slack-pricing
    routes:
    - match_re:
        severity: page|critical
      receiver: pagerduty-pricing
      continue: true
    - match:
        severity: ticket
      receiver: jira-pricing
      continue: true
    - receiver: slack-pricing
  - matchers:
    - team="storefront"
    receiver: slack-storefront
    routes:
    - matchers:
      - severity=~"page|critical"
      receiver: pagerduty-storefront
      continue: true
    - matchers:
      - severity="ticket"
      receiver: jira-storefront
      continue: true
    - receiver: slack-storefront
  - matchers:
    - team="product-catalog"
    receiver: slack-product-catalog-oncall
    routes:
    - matchers:
      - severity=~"page|critical"
      receiver: pagerduty-product-catalog
      continue: true
    - matchers:
      - severity="ticket"
      receiver: jira-product-catalog
      continue: true
    - receiver: slack-product-catalog-oncall
  - matchers:
    - team="checkout-core"
    receiver: slack-checkout-core
    routes:
    - matchers:
      - severity=~"page|critical"
      receiver: pagerduty-checkout-core
      continue: true
    - matchers:
      - severity="ticket"
      receiver: jira-checkout-core
      continue: true
    - receiver: slack-checkout-core
  - matchers:
    - team="growth"
    receiver: slack-growth
    routes:
    - matchers:
      - severity=~"page|critical"
      receiver: pagerduty-growth
      continue: true
    - matchers:
      - severity="ticket"
      receiver: jira-growth
      continue: true
    - receiver: slack-growth
  # teams below route alerts from the platform and data Prometheus servers
  - matchers:
    - team="storage"
    receiver: slack-storage
    repeat_interval: 1h
    routes:
    - matchers:
      - severity=~"page|critical"
      receiver: pagerduty-storage
      continue: true
    - matchers:
      - severity="ticket"
      receiver: jira-storage
      continue: true
    - receiver: slack-storage
  - matchers:
    - team="messaging"
    receiver: slack-messaging
    routes:
    - matchers:
      - severity=~"page|critical"
      receiver: pagerduty-messaging
      continue: true
    - matchers:
      - severity="ticket"
      receiver: jira-messaging
      continue: true
    - receiver: slack-messaging
  - matchers:
    - team="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="data-platform"
    receiver: slack-data-platform
    routes:
    - matchers:
      - severity=~"page|critical"
      receiver: pagerduty-data-platform
      continue: true
    - matchers:
      - severity="ticket"
      receiver: jira-data-platform
      continue: true
    # tickets and warnings per pod in Slack, so the channel shows which pod; pages group per service above
    - receiver: slack-data-platform
      group_by: [alertname, pod, service]
  - 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="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="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
    - receiver: slack-build-infra
  - 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
  # platform wanted tickets in Slack as well as Jira (OBS-1236)
  - matchers:
    - team="platform"
    receiver: slack-platform
    routes:
    - matchers:
      - severity=~"page|critical"
      receiver: pagerduty-platform
      continue: true
    - matchers:
      - severity="ticket"
      receiver: jira-platform
      continue: true
    - receiver: slack-platform
receivers:
- name: slack-alerts-default
  slack_configs:
  - channel: "#alerts-default"
    send_resolved: true
- name: slack-sre-fyi
  slack_configs:
  - channel: "#sre-fyi"
    send_resolved: false
- name: slack-prometheus-meta
  slack_configs:
  - channel: "#prometheus-meta"
- name: pagerduty-sre
  pagerduty_configs:
  - routing_key_file: /etc/alertmanager/secrets/pagerduty/sre
- name: pagerduty-build-infra
  pagerduty_configs:
  - routing_key_file: /etc/alertmanager/secrets/pagerduty/build-infra
- name: slack-build-infra
  slack_configs:
  - channel: "#build-infra-alerts"
    send_resolved: true
- name: jira-build-infra
  webhook_configs:
  - url: https://jira-bridge.corp.cartohale.example/hooks/build_infra
- name: pagerduty-checkout-core
  pagerduty_configs:
  - routing_key_file: /etc/alertmanager/secrets/pagerduty/checkout-core
- name: slack-checkout-core
  slack_configs:
  - channel: "#checkout-core-alerts"
    send_resolved: true
- name: jira-checkout-core
  webhook_configs:
  - url: https://jira-bridge.corp.cartohale.example/hooks/checkout_core
- 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.corp.cartohale.example/hooks/data_platform
- 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.corp.cartohale.example/hooks/edge
- name: pagerduty-growth
  pagerduty_configs:
  - routing_key_file: /etc/alertmanager/secrets/pagerduty/growth
- name: slack-growth
  slack_configs:
  - channel: "#growth-alerts"
    send_resolved: true
- name: jira-growth
  webhook_configs:
  - url: https://jira-bridge.corp.cartohale.example/hooks/growth
# routing key rotated in OBS-2394
- 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.corp.cartohale.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.corp.cartohale.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.corp.cartohale.example/hooks/network
- name: pagerduty-platform
  pagerduty_configs:
  - routing_key_file: /etc/alertmanager/secrets/pagerduty/platform
- name: slack-platform
  slack_configs:
  - channel: "#platform-alerts"
    send_resolved: true
- name: jira-platform
  webhook_configs:
  - url: https://jira-bridge.corp.cartohale.example/hooks/platform
- name: pagerduty-pricing
  pagerduty_configs:
  - routing_key_file: /etc/alertmanager/secrets/pagerduty/pricing
- name: slack-pricing
  slack_configs:
  - channel: "#pricing-alerts"
    send_resolved: true
- name: jira-pricing
  webhook_configs:
  - url: https://jira-bridge.corp.cartohale.example/hooks/pricing
- name: pagerduty-product-catalog
  pagerduty_configs:
  - routing_key_file: /etc/alertmanager/secrets/pagerduty/product-catalog
- name: slack-product-catalog
  slack_configs:
  - channel: "#product-catalog-alerts"
    send_resolved: true
- name: jira-product-catalog
  webhook_configs:
  - url: https://jira-bridge.corp.cartohale.example/hooks/product_catalog
- 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.corp.cartohale.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.corp.cartohale.example/hooks/storage
- name: pagerduty-storefront
  pagerduty_configs:
  - routing_key_file: /etc/alertmanager/secrets/pagerduty/storefront
- name: slack-storefront
  slack_configs:
  - channel: "#storefront-alerts"
    send_resolved: true
- name: jira-storefront
  webhook_configs:
  - url: https://jira-bridge.corp.cartohale.example/hooks/storefront
# unused since 2024, the SMTP relay it points at is gone
- name: email-oncall
  email_configs:
  - to: oncall@corp.cartohale.example
    send_resolved: false
- name: slack-product-catalog-oncall
  slack_configs:
  - channel: "#product-catalog-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]
- source_matchers:
  - alertname="CatalogApiDown"
  target_matchers:
  - alertname=~"CatalogApiErrorBudgetBurnFast|CatalogApiErrorBudgetBurnSlow|CatalogApiHighErrorRatio"
  equal: [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="order-events",container="order-events"} / container_spec_memory_limit_bytes{service="order-events",container="order-events"}) > 0.9
    for: 15m
    labels:
      severity: ticket
      team: checkout-core
    annotations:
      summary: "{{ $labels.service }} keeps running close to its memory limit"
      runbook_url: https://runbooks.corp.cartohale.example/alerts/ContainerMemoryNearLimit
  - alert: ContainerMemoryNearLimit
    expr: |
      max by (service) (container_memory_working_set_bytes{service="promo-worker",container="promo-worker"} / container_spec_memory_limit_bytes{service="promo-worker",container="promo-worker"}) > 0.9
    for: 15m
    labels:
      severity: ticket
      team: growth
    annotations:
      summary: "{{ $labels.service }} keeps running close to its memory limit"
      runbook_url: https://runbooks.corp.cartohale.example/alerts/ContainerMemoryNearLimit
  - alert: ContainerMemoryNearLimit
    expr: |
      max by (service) (container_memory_working_set_bytes{service="search-indexer",container="search-indexer"} / container_spec_memory_limit_bytes{service="search-indexer",container="search-indexer"}) > 0.9
    for: 15m
    labels:
      severity: ticket
      team: product-catalog
    annotations:
      summary: "{{ $labels.service }} keeps running close to its memory limit"
      runbook_url: https://runbooks.corp.cartohale.example/alerts/ContainerMemoryNearLimit
  - alert: ContainerMemoryNearLimit
    expr: |
      max by (service) (container_memory_working_set_bytes{service="catalog-worker",container="catalog-worker"} / container_spec_memory_limit_bytes{service="catalog-worker",container="catalog-worker"}) > 0.9
    for: 15m
    labels:
      severity: ticket
      team: product-catalog
    annotations:
      summary: "{{ $labels.service }} keeps running close to its memory limit"
      runbook_url: https://runbooks.corp.cartohale.example/alerts/ContainerMemoryNearLimit
AF_EOF
mkdir -p 'rules'
cat > 'rules/disk.yml' <<'AF_EOF'
# host disks (infra)
groups:
- name: disk
  rules:
  - alert: HostDiskAlmostFull
    expr: node_filesystem_avail_bytes{fstype!~"tmpfs|overlay"} / node_filesystem_size_bytes < 0.1
    for: "5m"
    labels: {severity: warning, team: infra}
    annotations:
      summary: "{{ $labels.instance }} {{ $labels.mountpoint }} is under 10% free"
      runbook_url: https://runbooks.corp.cartohale.example/alerts/HostDiskAlmostFull
AF_EOF
mkdir -p 'rules'
cat > 'rules/legacy-storefront.yml' <<'AF_EOF'
# storefront 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: storefront-records
  rules:
  - record: job:http_requests:rate5m
    expr: sum by (job, service) (rate(http_requests_total{service=~"cart-svc|promo-worker|returns-api"}[5m]))
  - record: job:http_errors:rate5m
    expr: sum by (job, service) (rate(http_requests_total{service=~"cart-svc|promo-worker|returns-api",code=~"5.."}[5m]))
- name: cart-svc
  rules:
  # threshold agreed with storefront in OBS-1698
  - alert: CartSvcHighErrorRatio
    expr: sum by (service) (rate(http_requests_total{service="cart-svc",code=~"5.."}[5m])) / sum by (service) (rate(http_requests_total{service="cart-svc"}[5m])) > 0.1
    for: "10m"
    labels: {severity: page, team: storefront}
    annotations:
      summary: "{{ $labels.service }} is failing {{ $value | humanizePercentage }} of requests"
      runbook_url: https://runbooks.corp.cartohale.example/alerts/CartSvcHighErrorRatio
  - alert: CartSvcLatencyHigh
    expr: histogram_quantile(0.99, sum by (service, le) (rate(http_request_duration_seconds_bucket{service="cart-svc"}[5m]))) > 0.5
    for: "10m"
    labels: {severity: warning, team: storefront}
    annotations:
      summary: "{{ $labels.service }} p99 above 500ms"
      runbook_url: https://runbooks.corp.cartohale.example/alerts/CartSvcLatencyHigh
  # TODO(2024) move to a latency SLO once we have one
  - alert: CartSvcLatencyHigh
    expr: histogram_quantile(0.99, sum by (service, le) (rate(http_request_duration_seconds_bucket{service="cart-svc"}[5m]))) > 1
    for: "10m"
    labels: {severity: critical, team: storefront}
    annotations:
      summary: "{{ $labels.service }} p99 above 1s"
      runbook_url: https://runbooks.corp.cartohale.example/alerts/CartSvcLatencyHigh
- name: promo-worker
  rules:
  - alert: PromoWorkerHighErrorRatio
    expr: sum by (service) (rate(http_requests_total{service="promo-worker",code=~"5.."}[5m])) / sum by (service) (rate(http_requests_total{service="promo-worker"}[5m])) > 0.1
    for: "10m"
    labels: {severity: page, team: growth}
    annotations:
      summary: "{{ $labels.service }} is failing {{ $value | humanizePercentage }} of requests"
      runbook_url: https://runbooks.corp.cartohale.example/alerts/PromoWorkerHighErrorRatio
  - alert: PromoWorkerLatencyHigh
    expr: histogram_quantile(0.99, sum by (service, le) (rate(http_request_duration_seconds_bucket{service="promo-worker"}[5m]))) > 0.5
    for: "10m"
    labels: {severity: warning, team: growth}
    annotations:
      summary: "{{ $labels.service }} p99 above 500ms"
      runbook_url: https://runbooks.corp.cartohale.example/alerts/PromoWorkerLatencyHigh
  # TODO(2024) move to a latency SLO once we have one
  - alert: PromoWorkerLatencyHigh
    expr: histogram_quantile(0.99, sum by (service, le) (rate(http_request_duration_seconds_bucket{service="promo-worker"}[5m]))) > 1
    for: "10m"
    labels: {severity: critical, team: growth}
    annotations:
      summary: "{{ $labels.service }} p99 above 1s"
      runbook_url: https://runbooks.corp.cartohale.example/alerts/PromoWorkerLatencyHigh
  - alert: PromoWorkerDbConnectionsHigh
    expr: max by (service) (db_pool_connections_active{service="promo-worker"} / db_pool_connections_max{service="promo-worker"}) > 0.8
    for: "5m"
    labels: {severity: warning, team: growth}
    annotations:
      summary: "{{ $labels.service }} is using over 80% of its DB pool"
      runbook_url: https://runbooks.corp.cartohale.example/alerts/PromoWorkerDbConnectionsHigh
  - alert: PromoWorkerDbConnectionsHigh
    expr: max by (service) (db_pool_connections_active{service="promo-worker"} / db_pool_connections_max{service="promo-worker"}) > 0.95
    for: "5m"
    labels: {severity: critical, team: growth}
    annotations:
      summary: "{{ $labels.service }} DB pool nearly exhausted"
      runbook_url: https://runbooks.corp.cartohale.example/alerts/PromoWorkerDbConnectionsHigh
  - alert: ReplicationLagHigh
    expr: max by (service) (pg_replication_lag_seconds{service="promo-worker"}) > 30
    for: "10m"
    labels: {severity: page, team: growth}
    annotations:
      summary: "{{ $labels.service }} replica is behind the primary"
      description: Replication lag is {{ $value | humanize }}s.
      runbook_url: https://runbooks.corp.cartohale.example/alerts/ReplicationLagHigh
- name: returns-api
  rules:
  - alert: ReturnsApiHighErrorRatio
    expr: sum by (service) (rate(http_requests_total{service="returns-api",code=~"5.."}[5m])) / sum by (service) (rate(http_requests_total{service="returns-api"}[5m])) > 0.02
    for: "10m"
    labels: {severity: page, team: storefront}
    annotations:
      summary: "{{ $labels.service }} is failing {{ $value | humanizePercentage }} of requests"
      runbook_url: https://runbooks.corp.cartohale.example/alerts/ReturnsApiHighErrorRatio
  - alert: ReturnsApiLatencyHigh
    expr: histogram_quantile(0.99, sum by (service, le) (rate(http_request_duration_seconds_bucket{service="returns-api"}[5m]))) > 0.5
    for: "10m"
    labels: {severity: warning, team: storefront}
    annotations:
      summary: "{{ $labels.service }} p99 above 500ms"
      runbook_url: https://runbooks.corp.cartohale.example/alerts/ReturnsApiLatencyHigh
  - alert: ReturnsApiLatencyHigh
    expr: histogram_quantile(0.99, sum by (service, le) (rate(http_request_duration_seconds_bucket{service="returns-api"}[5m]))) > 1
    for: "10m"
    labels: {severity: critical, team: storefront}
    annotations:
      summary: "{{ $labels.service }} p99 above 1s"
      runbook_url: https://runbooks.corp.cartohale.example/alerts/ReturnsApiLatencyHigh
  - alert: ReturnsApiDbConnectionsHigh
    expr: max by (service) (db_pool_connections_active{service="returns-api"} / db_pool_connections_max{service="returns-api"}) > 0.8
    for: "5m"
    labels: {severity: warning, team: storefront}
    annotations:
      summary: "{{ $labels.service }} is using over 80% of its DB pool"
      runbook_url: https://runbooks.corp.cartohale.example/alerts/ReturnsApiDbConnectionsHigh
  - alert: ReturnsApiDbConnectionsHigh
    expr: max by (service) (db_pool_connections_active{service="returns-api"} / db_pool_connections_max{service="returns-api"}) > 0.95
    for: "5m"
    labels: {severity: critical, team: storefront}
    annotations:
      summary: "{{ $labels.service }} DB pool nearly exhausted"
      runbook_url: https://runbooks.corp.cartohale.example/alerts/ReturnsApiDbConnectionsHigh
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: CatalogApiDown
    expr: |
      sum by (service) (up{service="catalog-api"}) == 0
      or absent(up{service="catalog-api"})
    for: 3m
    labels:
      severity: page
      team: product-catalog
    annotations:
      summary: catalog-api has no healthy scrape targets
      runbook_url: https://runbooks.corp.cartohale.example/alerts/CatalogApiDown
  - alert: CartSvcDown
    expr: |
      sum by (service) (up{service="cart-svc"}) == 0
      or absent(up{service="cart-svc"})
    for: 3m
    labels:
      severity: page
      team: storefront
    annotations:
      summary: cart-svc has no healthy scrape targets
      runbook_url: https://runbooks.corp.cartohale.example/alerts/CartSvcDown
  - alert: PromoWorkerDown
    expr: |
      sum by (service) (up{service="promo-worker"}) == 0
      or absent(up{service="promo-worker"})
    for: 3m
    labels:
      severity: page
      team: growth
    annotations:
      summary: promo-worker has no healthy scrape targets
      runbook_url: https://runbooks.corp.cartohale.example/alerts/PromoWorkerDown
  - alert: SearchIndexerDown
    expr: |
      sum by (service) (up{service="search-indexer"}) == 0
      or absent(up{service="search-indexer"})
    for: 3m
    labels:
      severity: page
      team: product-catalog
    annotations:
      summary: search-indexer has no healthy scrape targets
      runbook_url: https://runbooks.corp.cartohale.example/alerts/SearchIndexerDown
  # for: 3m so a rolling restart doesn't page; pricing-svc cycles one pod at a time
  - alert: PricingSvcDown
    expr: |
      sum by (service) (up{service="pricing-svc"}) == 0
      or absent(up{service="pricing-svc"})
    for: 3m
    labels:
      severity: page
      team: pricing
    annotations:
      summary: pricing-svc has no healthy scrape targets
      runbook_url: https://runbooks.corp.cartohale.example/alerts/PricingSvcDown
  - alert: ReturnsApiDown
    expr: |
      sum by (service) (up{service="returns-api"}) == 0
      or absent(up{service="returns-api"})
    for: 3m
    labels:
      severity: page
      team: storefront
    annotations:
      summary: returns-api has no healthy scrape targets
      runbook_url: https://runbooks.corp.cartohale.example/alerts/ReturnsApiDown
  - alert: InventorySvcDown
    expr: |
      sum by (service) (up{service="inventory-svc"}) == 0
      or absent(up{service="inventory-svc"})
    for: 3m
    labels:
      severity: page
      team: product-catalog
    annotations:
      summary: inventory-svc has no healthy scrape targets
      runbook_url: https://runbooks.corp.cartohale.example/alerts/InventorySvcDown
  - alert: CatalogWorkerDown
    expr: |
      sum by (service) (up{service="catalog-worker"}) == 0
      or absent(up{service="catalog-worker"})
    for: 3m
    labels:
      severity: page
      team: product-catalog
    annotations:
      summary: catalog-worker has no healthy scrape targets
      runbook_url: https://runbooks.corp.cartohale.example/alerts/CatalogWorkerDown
AF_EOF
mkdir -p 'rules'
cat > 'rules/slo-cart-svc.yml' <<'AF_EOF'
groups:
- name: slo-cart-svc
  rules:
  - alert: CartSvcErrorBudgetBurnFast
    expr: |
      slo:sli_error:ratio_rate1h{service="cart-svc"} > (3.36 * 0.005)
      and slo:sli_error:ratio_rate5m{service="cart-svc"} > (3.36 * 0.005)
    for: 2m
    labels:
      severity: page
      team: storefront
      slo: cart-svc-availability
    annotations:
      summary: "{{ $labels.service }} is spending its error budget fast"
      runbook_url: https://runbooks.corp.cartohale.example/alerts/CartSvcErrorBudgetBurnFast
  - alert: CartSvcErrorBudgetBurnSlow
    expr: |
      slo:sli_error:ratio_rate6h{service="cart-svc"} > (1.4 * 0.005)
      and slo:sli_error:ratio_rate30m{service="cart-svc"} > (1.4 * 0.005)
    for: 15m
    labels:
      severity: ticket
      team: storefront
      slo: cart-svc-availability
    annotations:
      summary: "{{ $labels.service }} is spending its error budget steadily"
      runbook_url: https://runbooks.corp.cartohale.example/alerts/CartSvcErrorBudgetBurnSlow
AF_EOF