In the world of professional streaming and telecom, quality monitoring is always a trade-off. We want total visibility into our streams, but we don't want the monitoring process itself to interfere with content delivery.
Traditional monitoring often relies on Relays or Proxies. While convenient, these methods have a significant downside: they create extra links in the chain, add latency, and double the load on the source.
Today we’re diving into a more elegant approach: non-intrusive monitoring. Let’s explore how to "observe" a session without breaking it or bloating your traffic.
What is Non-Intrusive Monitoring?
In short, it’s the ability to monitor an existing session between a source and a receiver from the sidelines. The probe (monitoring software) doesn't establish a separate connection and doesn't act as an active intermediary like a proxy.
✅ Why It’s a Game Changer
Targeted monitoring. The probe watches only the session you need — nothing extra.
No traffic duplication. No second session is created, so the load on the source doesn't increase.
No relay/proxy. No additional latency, no extra points of failure.
⚠️ Limitations
Expertise required. Configuring the probe and network equipment calls for a network engineer's skills.
Slight data discrepancy. Probe readings may differ slightly from metrics on the receiver side. Still, this is more accurate than creating a separate monitoring session.
Setup isn't always straightforward. Configuring monitoring tasks requires attention.
Encryption adds complexity. Monitoring encrypted streams may be limited or impossible.
That said, in most practical scenarios, the advantages clearly outweigh the limitations.
Three Ways to Access Data
Non-intrusive monitoring can be implemented in several ways depending on your infrastructure. The core principle stays the same: no separate session is created, and already-established sessions are not interrupted.
1. Network TAP
A Network TAP (Test Access Point) is a hardware device physically inserted into a network cable to passively copy all traffic in both directions.
It provides a faithful copy of the traffic, unlike SPAN ports, which may drop packets. Key limitation: additional hardware is required, physically splitting the network. This introduces a new point of failure — a factor that can't be ignored when designing fault-tolerant infrastructure.
2. Port Mirroring (SPAN)
SPAN (Switched Port Analyzer) is a feature built into virtually all modern switches. It copies packets from one or more ports to a designated destination port, where the monitoring device is connected.
The main advantage: no additional hardware needed — the switch is usually already in the network.
However, SPAN has a potential issue — packet loss on the mirrored port. This can happen for two reasons:
The mirrored port has lower priority than others and drops packets first under heavy load.
The combined volume of mirrored traffic may exceed the bandwidth of the destination port.
For most monitoring tasks, SPAN offers the best balance between ease of deployment and functionality.
3. Installing Directly on the Source or Receiver
If the source or receiver is software running on an x86-compatible machine with Windows or Linux, the probe can be installed right there.
In this configuration, the computer's own network subsystem effectively acts as a Network TAP — no additional hardware needed. This is the simplest path when the infrastructure allows it.
Conclusions
Non-intrusive monitoring of the SRT protocol is a highly effective solution that addresses a long-standing industry need. Despite certain limitations and greater configuration complexity compared to standard method, its advantages outweigh the drawbacks.
One additional important factor should be emphasized: the cost of non-intrusive monitoring is practically identical to that of conventional approach, since it does not require increased probe hardware performance.
If you'd like to learn more about specific use cases or technical details, explore the full article.
