A bank's on-call rotation wants a page when a threshold is crossed and does not want a ticket or a telemetry feed. Which handoff fits?
Select an answer to reveal the explanation.
Short Explanation
If the night guard only asked for a buzzer, a bound report on the desk is extra furniture. You send an alert-threshold page, because the bank's on-call rotation asked only for that page. A polling API, an OpenTelemetry stream, or an ITSM ticket hands the condition to someone who did not ask for it.
Full Explanation
The on-call rotation asked for a page when a threshold is crossed, and it declined both a ticket and a telemetry feed. The matching handoff is an alert threshold that notifies that rotation and stops there. A polling API serves a dashboard that pulls data. The rotation will not watch a dashboard during the incident, so an API does not deliver the page they asked to receive. OpenTelemetry streams the condition into a metrics pipeline. That is the telemetry feed they said they do not want for this purpose, even if other teams consume telemetry for trending. An ITSM ticket opens work in a service-desk queue they did not request. A ticket can be the right handoff for a desk that owns incident records, and this rotation asked not to get one. Extra deliveries create noise and a second place to look. Give this audience the threshold page alone. Exam caveat: the correct integration is the one the receiving team will act on, and a page is not improved by attaching the handoffs they refused. Operational check: cross the condition in a test and confirm on-call receives a single threshold page, with no ticket and no telemetry requirement for that rotation.