Track VPN pressure history
This commit is contained in:
@@ -479,6 +479,10 @@ The `flow_pressure` summary includes a `recommended_action` such as
|
||||
contract, so heartbeat reports and smoke diagnostics consume the same runtime
|
||||
decision.
|
||||
The scheduler's nominal snapshot explicitly reports the `observe` action.
|
||||
Flow-scheduler snapshots keep a bounded pressure transition history with the
|
||||
observed level, score, reasons, and recommended action. Repeated snapshots do
|
||||
not duplicate unchanged pressure states, so controllers can distinguish current
|
||||
state from recent worsening or recovery without unbounded heartbeat growth.
|
||||
`mesh-live-smoke` reports the recommended action for its mixed bulk/interactive
|
||||
load scenario.
|
||||
Nodes advertise the `vpn_fabric_flow_pressure` capability when that heartbeat
|
||||
|
||||
Reference in New Issue
Block a user