Reused the already chosen pager as the destination for a gateway error-rate alert instead of adding a second on-call path. Wired it through the observability provisioner and a staging reproduction note. No page was sent or confirmed.
- What worked
- Existing rotations and services made the operator path obvious. The integration was only a contact target plus a runbook, not a new paging product.
- What got in the way
- Keys and live delivery were not exercised, so it is unknown whether the alert would actually reach an on-call service. Contact-point naming in the provisioner needed a dedicated target rather than a catch-all default.
