I ran the circuit breaker demo from the blog post and I didn't get the expected otuput:

./docker-run.sh -d circuit-breaker                                         

circuit-breaker
63b4b5c03715d64ee6bc8a8ca4b4fc4c8795dd21aa42034421d39a0c66ffedd1

docker exec -it client bash -c 'java -jar http-client.jar'                   

using num threads: 1
Starting pool-1-thread-1 with numCalls=5 parallelSends=false delayBetweenCalls=0 url=http://localhost:15001/get mixedRespTimes=false
pool-1-thread-1: successes=[0], failures=[5], duration=[15418ms]

I'm running this on MacOS 10.15.2.

Hi,

I am trying to run the demo by following command

./docker-run.sh -d circuit-breaker

The container exits and upon looking into the logs it says : Unable to read file : /etc/envoy/envoy.json

Kindly please help to resolve this.

I am running Docker on Windows.

On the blog articles that correspond to this repository the table of contents indicates that Prometheus metrics exposition was intended as the fourth (next) article in the series.

I'm very interested in Prometheus exposition from Envoy, and I'm wondering if you could give me a hint about how you were planning to go about it. I have a couple of thoughts so far. First, I see that Envoy's native /stats endpoint on the admin port is a bit like statsd output.

1. I was thinking a bit about using the Prometheus statsd-exporter in order to provide a sink for Envoy to flush to, but I'm not yet familiar enough with the Envoy stats format to have a sense of how many rules would be called for to extract the varying portions of the stat names.
2. Envoy itself could be extended to natively provide metrics in Prometheus's exposition format. I'm not yet familiar enough with the codebase to have a sense of how much effort would be called for to take this approach, though the docs signal that it shouldn't be too hard.

What do you think? Were you imagining going for one of the above approaches, or do you have something else in mind? I'm interested to implement this (depending on effort required), so if you have a thought of a good route, I may come back shortly with a pull request.

The master release is no more inline with the circuit breaking demo and the docker image ceposta/http-envoy-client because the envoy.json does not contain the circuit_breakers configuration anymore:
https://blog.christianposta.com/microservices/01-microservices-patterns-with-envoy-proxy-part-i-circuit-breaking/
the consequence is sending the traffic directly to Envoy Proxy using (docker exec -it client bash -c 'java -jar http-client.jar') fails.

To succeed with the circuit breaking demo, the commit from 2 years ago has to be used:
https://github.com/christian-posta/envoy-microservices-patterns/tree/fb80cfb2b11b80f68c7acb561caf77c874d5d687

https://github.com/vbatts/envoy-examples/front-proxy/Dockerfile-frontenvoy

also, then you could add things like java to the image for your client demo