Metrics

The Duo Stream Integration plugin provides the following metric in addition to the shared observable metrics.

StreamTraffic

OS:

🪟 Windows

StreamTraffic reports activity at a Duo instance’s streaming service. It is available only on an Instance that has a network-service watch. It differs from Traffic, which measures transfers attributed to the session’s processes.

watchStreamTraffic

default:

true

Enables the metric on DuoSessionMonitor; individual instances can override this setting. Disabling it removes StreamTraffic from the available expression operands. Session and process metrics remain available, and incoming requests can still start an instance.

minStreamTraffic

inherited:

Overrides the streaming-service threshold for one Instance. Without a threshold, activity follows the service’s normal connection detection.

Streaming thresholds require packet capture on the interface carrying the client’s traffic. Select Capture through watchMode, or use automatic traffic selection with a configured NetworkMonitor. Listener mode detects connections but rejects streaming thresholds. See Demand detection.

Formats

Both threshold attributes accept the following network-traffic formats:

10

A number specified without any unit declares an amount of raw packets that have to be counted during the configured timeout of the System Monitor, otherwise the node will be considered idle.

100/s

A number specified with a time period but without a binary unit declares an amount of raw packets that have to be counted in average during the configured timeout of the System Monitor, otherwise the node will be considered idle.

1MB/s

A number specified with both a time period and a binary unit declares an amount of bytes that have to be counted in average during the configured timeout of the System Monitor, otherwise the node will be considered idle.

100kb

A number specified without a time period, but with a binary unit declares an amount of bytes that have to be counted during the configured timeout of the System Monitor, otherwise the node will be considered idle.

Example

While using packet capture, you can use this fragment inside DuoSessionMonitor, to have recent user input or streaming traffic keep the instance active:

<Instance name="Neo" watch="Input or StreamTraffic"
          maxLastInputTime="10min"
          minStreamTraffic="1MB/s" />

Replace Neo with the internal instance name from Duo. The streaming threshold measures average traffic during the inspection interval. See Watch expressions for expression syntax and composition.