Strategies
Suppressed
Probabilistic shedding that increases as a key approaches or exceeds its target rate.
Choose the suppressed strategy when a hard cliff is too abrupt and you would rather shed load progressively.
What it does
Suppressed mode estimates how overloaded a key is and computes a suppression_factor between 0.0 and 1.0.
0.0means no suppression pressure- values closer to
1.0mean stronger shedding pressure
The decision shape is:
AllowedSuppressed { is_allowed, suppression_factor }
Always check is_allowed.
When to use it
- graceful degradation under overload
- traffic smoothing when dropping everything at once is too harsh
- systems that can tolerate some requests being denied probabilistically
What to expect
- below the limit, behavior looks similar to normal admission
- near or above the limit, a growing fraction of requests are denied
- the strategy still exposes useful state through
get_suppression_factor(...)
If you need a strict boundary instead, use the absolute strategy.