1.9 KiB
gateway-heartbeat-telemetry Specification
Purpose
Define truthful measured gateway egress, disjoint delay semantics, and bounded authenticated heartbeat telemetry.
Requirements
Requirement: Heartbeat egress is observed
Authenticated gateway heartbeat telemetry SHALL calculate egress from monotonic transmitted-byte deltas over monotonic elapsed time and MUST NOT report configured capacity as measured traffic.
Scenario: Controlled byte delta is sampled
- WHEN transmitted bytes increase by a known amount during a known interval
- THEN heartbeat egress equals the measured rate while configured capacity remains a separate registration value
Requirement: Required telemetry remains bounded and low cardinality
The established authenticated path SHALL expose observed bytes, packets, drops, RTT, loss, jitter, queue delay, processing delay, pacing, reconnect, and provider state without session, route, credential, or payload labels.
Scenario: Telemetry snapshot is published
- WHEN the gateway emits a heartbeat after forwarding traffic
- THEN it carries the bounded process-level observations and no high-cardinality or secret-bearing value
Requirement: Production delays have disjoint sample semantics
Queue delay SHALL measure provider-queue residence, processing delay SHALL measure provider recovery plus framing and QUIC handoff work excluding queue and pacing, and pacing delay SHALL measure scheduler waiting only. The gateway SHALL advance processing samples once per complete provider media unit even when it emits multiple Verse frames.
Scenario: Known production waits
- WHEN one provider media unit has controlled enqueue, processing, and pacing intervals and fragments across multiple frames
- THEN each cumulative total reports only its intended interval and exactly one processing sample is retained through authenticated Server persistence