A retailer's metrics pipeline asks to receive OpenTelemetry and says it does not want a ticket. Which handoff should the assurance team use?
Select an answer to reveal the explanation.
Short Explanation
The warehouse asked for a conveyor, not a clipboard dropped on a desk. You send OpenTelemetry because the retailer's metrics pipeline asked for that stream and not a ticket. An ITSM ticket, a polling API, or an alert-threshold page delivers the condition to a different kind of consumer.
Full Explanation
The metrics pipeline asked for OpenTelemetry and explicitly rejected a ticket. The matching handoff is a telemetry stream the pipeline can ingest alongside the rest of its retailer metrics. An ITSM ticket puts the condition into an incident queue. That is the delivery the pipeline said it does not want, and a queue is not a telemetry feed. A polling API waits for a client to scrape data on some schedule. The pipeline asked to receive a stream, not to become a poller, so an API shifts the work onto a pattern they did not request. An alert-threshold page notifies on-call and skips the pipeline. On-call may still want pages for other conditions, but this request was for telemetry into the metrics system. Match the handoff to the consumer that will actually use the data. Exam caveat: OpenTelemetry, an API, an alert threshold, and ITSM solve different handoffs, and a ticket is the one this pipeline refused. Operational check: confirm the pipeline is ingesting the telemetry and that no ticket was opened for this feed.