Developers aren’t big fans of writing logs. This is because when writing code we feel logs don’t bring any value - Our code is good, we understand it, so why do we need logs in here!??!

Sadly we understand why we need logs when it’s too late - When the system is down (at 3 am), Or when a customer is facing some massive bug.

More than that the first “person” to read your logs in today ecosystem (cloud/lambda/k8s) is no longer human, It’s a machine! Therefore your logging infrastructure should be written in accordance.

This talk will cover:

• how to format a logs
• Why Logs that ‘people read’ doesn’t scale
• Causality and correlation.
• Distributed tracing to the help.
• Telling a story using logs Come and find out what’s broken in logging design, and how to fix it :)