Just came across something related for amazon lambda:
https://medium.freecodecamp.org/how-to-implement-log-aggregation-for-aws-lambda-ca714bf02f48
Quote:
During the execution of a Lambda function, whatever you write to stdout
(for example, using|console.log|in Node.js) will be captured by Lambda and
sent to CloudWatch Logs asynchronously in the background.
Still does not answer the "Why" on the performance question, but I thought it
was interesting ...
Cheers,
Ole
On 04/03/2018 04:25 PM, Ralph Goers wrote:
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 file, even when stdout is redirected to a file. What I am
wondering, and still haven’t found an answer to, is whether this performance
degradation is present when a Java app is running in a docker container and
logs to stdout.
Ralph
On Apr 3, 2018, at 11:44 AM, Ole Ersoy <[email protected]> wrote:
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:
http://callistaenterprise.se/blogg/teknik/2017/07/29/building-microservices-part-7-distributed-tracing/
http://callistaenterprise.se/blogg/teknik/2017/09/13/building-microservices-part-8-logging-with-ELK/
These cover log event collection for both ELK and Zipkin. Parts 1-6 in the
series are really good as well if you want to know more about microservices and
security in general with the Spring and Netflix OSS stack. Originally came
across it while looking for OAuth material.
Cheers,
Ole
