Jose A. Iñigo

Any updates on this?

@howardjohn Thanks for clearing it up. Just one question why isn't 500 status code included in the circuit breaking? In my view a service that returns continuously Internal Server Errors...

I understand the motivation now however I think there's another valid scenario that is not supported. In our microservice infrastructure we were relying on Hystrix as an application circuit breaker....

Envoy explicitly distinguishes between consecutive gateway failures (502,503,504) errors and consecutive errors (5xx), supporting both of them. https://www.envoyproxy.io/docs/envoy/v1.5.0/intro/arch_overview/outlier Istio’s consecutiveErrors field is therefore misleading, shouldn’t it be aligned with Envoys...