Re: Container Log Collection for Microservices

Yes, at least that way it shouldn’t impact the throughput of your application unless you are logging so much that whatever buffer or queueing it uses doesn’t fill up. Ralph > On Apr 3, 2018, at 9:30 PM, Ole Ersoy wrote: > > Just came across something related for amazon

Re: Container Log Collection for Microservices

Just came across something related for amazon lambda: https://medium.freecodecamp.org/how-to-implement-log-aggregation-for-aws-lambda-ca714bf02f48 Quote: Dur­ing the exe­cu­tion of a Lamb­da func­tion, what­ev­er you write to std­out (for example, using|console.log|in Node.js) will be

Re: Container Log Collection for Microservices

I plan on playing with the microservices from the tutorial more in the near future.  I could: 1) Load test one microservice without stdout logging 2) Load test with stdout logging 3) See if there is any response degradation recorded by zipkin Would be nice to see if Prometheus records any

Re: Container Log Collection for Microservices

Thanks. That is helpful but it still doesn’t answer the question I was asking, although it does provide good documentation on what people are recommending for how to configure applications for the cloud. Testing at Log4j has shown that writing to stdout is magnitudes slower than logging to a

Container Log Collection for Microservices

I accidentally deleted the original thread, but saw that there were some questions surrounding logging to stdout (I assume while running in a microservice dockerized environment). You might find these article helpful: