A manufacturer's service desk works only from its ticket queue and has said it will not read a telemetry stream. Which handoff should assurance use for that desk?
Select an answer to reveal the explanation.
Short Explanation
A service desk is like a shop that accepts work orders and will not watch every gauge in the plant. You hand this manufacturer's desk an ITSM ticket, because that team will not read a telemetry stream. An API, an alert with the raw stream attached, or an OpenTelemetry export still asks them to consume measurements they refused.
Full Explanation
The receiving team decides the handoff. This service desk already works from a ticket queue and has refused to read a telemetry stream, so the matching integration is an ITSM ticket in that queue. A pull API still requires the desk to poll measurements, which is the stream-reading job they declined. An alert threshold with the raw telemetry attached to each notice delivers the same stream in another wrapper and assumes someone on the desk will interpret samples. An OpenTelemetry export is the right handoff for a team that wants metrics in a pipeline, and it is the wrong handoff for a desk that will not consume telemetry at all. Exam caveat: pick the handoff from what the receiving team asked to work, not from which integration is newest. Operational check: confirm a new assurance condition opens a ticket in the desk's existing queue and that the desk can assign it without subscribing to a metric feed. If the only record is a stream nobody reads, the handoff missed the team. The ticket is something the desk can assign and close with the process it already runs.