SrtPcapProbeStats interface

Experimental. Passive-probe SRT stats for a pcap-derived SRT input (input.srt-pcap / input.srt-capture); present on SrtConnectionHealth only for those inputs, absent for live SRT. The probe infers these from captured SRT control traffic, so several fields are only observable with a suitable capture; a field the capture cannot observe is undefined (NOT 0) — the "not observable" contract.

Signature:

export interface SrtPcapProbeStats

Properties

Property Type Description

ackRttLastUs?

number

(Optional) the RTT the receiver wrote into its last numbered ACK, microseconds; undefined if none seen

bitrateBps?

number

(Optional) estimated payload bitrate, bits/s; undefined before two timed data packets

captureLossSuspected

number

post-ARQ declared-lost the receiver ACKed past — it had the packet, so the capture (our tap) missed it, not the network. A high value means the loss figures are suspect because the tap is dropping packets.

gaps

number

reassembly gap events observed

jitterUs?

number

(Optional) RFC 3550 interarrival jitter over data packets, microseconds; undefined before two packets

linkCapacityPps?

number

(Optional) the receiver’s estimated link capacity from the last full ACK, packets/s; undefined if none

nakReportedLost

number

pre-ARQ loss the receiver reported in NAKs (distinct sequence numbers)

networkLoss

number

post-ARQ declared-lost named by a NAK or DROPREQ (genuine network loss)

tapRttMaxUs?

number

(Optional) tap round-trip max, microseconds; undefined if not observable

tapRttMeanUs?

number

(Optional) tap round-trip (ACK → ACKACK at the tap) mean, microseconds; undefined if not observable

tapRttMinUs?

number

(Optional) tap round-trip min, microseconds; undefined if not observable

unattributedLoss

number

post-ARQ declared-lost with no evidence either way