At a logistics hub, the data-science group refuses tickets and wants measurements pushed continuously into the pipeline it already runs, not a poll it would have to build. Which handoff matches that request?
Select an answer to reveal the explanation.
Short Explanation
The data-science group wants the gauge readings piped to their bench, not a stack of work tickets. You export the logistics hub metrics with OpenTelemetry, because that is the stream they asked to receive. A poll API, an alert threshold, or an ITSM ticket does not push the series into their pipeline.
Full Explanation
A handoff matches the consumer. This group refused tickets and asked for measurements pushed continuously into a pipeline it already runs, which is an OpenTelemetry export of the metric stream. A request-response API would make the group poll for each sample, and they explicitly did not want to build a poll. An alert threshold that sends a notice only when one metric crosses it delivers exceptions, not the continuous series their pipeline is meant to analyze. An ITSM ticket for each interval is the handoff they refused, and a ticket is not a metric stream. Exam caveat: an API can feed a team that wants to pull data, but it is the wrong choice when the request is a push into an existing pipeline. Operational check: confirm samples arrive in the group's pipeline without a ticket being opened and without the group polling for each interval. If the only output is a notice or a ticket, the stream they asked for was not delivered. The export should show up as a continuous series in their pipeline, with no ticket opened and no poller they have to build.