Watch without touching the stream

A tap probe sits beside the stream: it receives, analyses and reports, and passes nothing on. Nothing downstream depends on it, so it can be added to a live path and taken away again without the path changing shape.

01 Described in config

A tap is a product template — a transport, a port, a stream id — stored beside the multi-source wall that probe publishes by default. The web form and the JSON file describe the same thing, so a template can be built either way.

02 Launched and waiting

The launched probe, healthy, listening on the transport its template named, with nothing to analyse yet. Healthy is not the same as running a workflow: the probe’s own API is the surface that knows.

03 It picks the stream up

Point a stream at it and the probe starts analysing. Stop the stream and it notices the source go away — it is watching, not latching.

Seen in: The operator view, A probe on an SRT feed