The alert that woke the wrong person for a year

A routing rule sending database alerts to a person who left the database team in 2023.

route:
  routes:
    - match: { team: data }
      receiver: pagerduty-data

receivers:
  - name: pagerduty-data
    pagerduty_configs:
      - service_key: ...      # a personal integration
                              # key, created 2022

A personal integration key survives a role change invisibly, because nothing about it is named after a person. Routing to a rota rather than to a key is the fix and the general rule is that any alert destination should be a role — checking the destinations after somebody changes team is a step that belongs in a leavers checklist and was not in ours.