Flow Purge Telemetry
The Flow Purge telemetry is emitted when a tracked flow is removed from the engine, typically after normal connection closure (TCP), inactivity timeout, or internal purge conditions. It captures final flow counters and end-state details at the point the flow leaves active tracking.
Use this record for post-session analysis, accounting, and flow lifecycle validation. Comparing purge records with periodic flow_stats updates helps explain why sessions ended and whether termination behavior aligns with network expectations.
Requirements
Flow Purge telemetry was introduced in the Core Plugin in version 1.0.20. To begin streaming the telemetry:
- Install and configure the Netify Agent
- Install and configure a Sink Plugin for receiving the telemetry
- Install and configure the Core Plugin and add stream-flows to types
- Source
- Core Plugin
- Plugin Release
- 1.0.20
Attributes
type
stringinterface
stringinternal
booleanreason
stringflow
objectflow.detection_packets
integerflow.digest
stringflow.digest_prev
array[string]flow.last_seen_at
integerflow.local_bytes
integerflow.local_packets
integerflow.local_rate
integerflow.other_bytes
integerflow.other_packets
integerflow.other_rate
integerflow.tcp
objectflow.tcp.resets
integerflow.tcp.retrans
integerflow.tcp.seq_errors
integerflow.total_bytes
integerflow.total_packets
integerFlow Purge Attributes - Example
{
"flow": {
"detection_packets": 12,
"digest": "fb69e87ed3b...",
"digest_prev": [
"d7fddd35cc27..."
],
"last_seen_at": 1772665905392,
"local_bytes": 0,
"local_packets": 0,
"local_rate": 387,
"other_bytes": 0,
"other_packets": 0,
"other_rate": 300,
"tcp": {
"resets": 0,
"retrans": 0,
"seq_errors": 0
},
"total_bytes": 13968,
"total_packets": 51
},
"interface": "wlp3s0",
"internal": true,
"reason": "closed",
"type": "flow_purge"
}