Classify VPN scheduler pressure
This commit is contained in:
@@ -461,6 +461,10 @@ timing and switch count.
|
||||
Common route switch reasons are bucketed into stable labels such as timeout,
|
||||
peer_unavailable, connection_refused, connection_reset, no_route_to_host, and
|
||||
capacity_limited to keep heartbeat cardinality bounded.
|
||||
Flow-scheduler snapshots now include a machine-readable pressure level
|
||||
(`nominal`, `warning`, `critical`) and bounded reason list derived from drops,
|
||||
route failures, route recovery, slow channels, bulk pressure, and adaptive
|
||||
backpressure.
|
||||
Endpoint ranking treats `capacity_limited` observations as a soft pressure
|
||||
penalty instead of a hard recent failure, enabling load spreading without
|
||||
marking the carrier unhealthy.
|
||||
|
||||
Reference in New Issue
Block a user