You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Currently, success rate is derived only from the HTTP response status codes of a dependency. This heuristic is effective when response latency is relatively fast, however in the situation when a dependency’s response latency is degraded, this would be useful.
The text was updated successfully, but these errors were encountered:
@marcusoyang I'm happy to explore this with you. Have you taken a look at Adaptive Concurrency
Control? That mechanism uses sampled latencies to make adjustments to the concurrency limit (essentially circuit breaking) thresholds.
I'm curious whether that meets your requirements and if not, why.
tl:dr
Add latency statistics into the Admission Control filter success rate calculation
Context
To make the Admission Control capability more effective in the context of slow dependency response times, the proposal is to add to the Admission Control filter envoy/source/extensions/filters/http/admission_control at main · envoyproxy/envoy and add response latency statistics in its successRateThreshold calculation.
Currently, success rate is derived only from the HTTP response status codes of a dependency. This heuristic is effective when response latency is relatively fast, however in the situation when a dependency’s response latency is degraded, this would be useful.
The text was updated successfully, but these errors were encountered: