In containerized applications, the ephemeral nature of these workloads add a key dimension to making the logs useful: CONTEXT. Our talk showcases some standard patterns to ensure the logging in Containers and Kubernetes has a PRECISE CONTEXT regardless of the logging solutions used by the end users.

1. Logging in a Container
World
Ramesh Podila & Ragu Srinivasan

4. •Great minds think alike
•Jack of all trades, master of none
•Curiosity killed the cat

5. •Great minds think alike, but fools rarely differ
•Jack of all trades, master of none, but better than
a master of one
•Curiosity killed the cat but satisfaction brought it
back

6. Logging for Containers
…With CONTEXT!!

7. Docker Logging
• Docker Logging Driver
• Streaming StdOut & StdErr
• Plan storage capacity
• Still logging to files?
• Use logging libraries !!

8. Kubernetes Logging
• Kubelet magic - /var/log/containers
• Read only access!!
• Added Complexity?
• Respawned containers for applications
• Containers scheduled on different hosts

9. Solutions
• Fluentd
• Fluentbit
• Beats
• But what about the all important CONTEXT ?

10. Context Plugins
• Beats
• add_kubernetes_metadata
• Fluentd
• fluent-plugin-kubernetes_metadata_filter
• Fluentbit
• Kubernetes Filter
POD Name
POD ID
Namespace
Container Name
Container ID
Labels
Annotations

11. Log like a Champ!!
• Go beyond Application logging
• Metrics
• Tracing Spans
• Few Solutions we like
• EFK
• Splunk
• Haystack

12. Questions?

13. Thanks!!