Getting Started with Logging in Kubernetes - Eduardo Silva, Treasure Data (Any Skill Level)

Want to view more sessions and keep the conversations going? Join us for KubeCon + CloudNativeCon North America in Seattle, December 11 - 13, 2018 (bit.ly/KCCNCNA18) or in Shanghai, November 14-15 (bit.ly/kccncchina18).
Getting Started with Logging in Kubernetes - Eduardo Silva, Treasure Data (Any Skill Level)
A good practice when deploying applications in Kubernetes is to set proper instrumentation to gather insights and solve general monitoring needs. Logging is a fundamental piece of the instrumentation cycle and is continually evolving to solve pains associated with unstructured formats, performance and monitoring. In this presentation you will learn the concepts involved in log processing for containerized applications. You will also be introduced to these hot new features in Logging: metering the logging pipeline with Prometheus, performance improvements, scalability and the ability to customize the log processor behavior through declarative resource annotations.
About Eduardo
Eduardo is an Open Source Software Engineer at Treasure Data. He currently leads the efforts to make logging more scalable in Containerized and Orchestrated systems such as Kubernetes.
Join us for KubeCon + CloudNativeCon in Barcelona May 20 - 23, Shanghai June 24 - 26, and San Diego November 18 - 21! Learn more at kubecon.io. The conference features presentations from developers and end users of Kubernetes, Prometheus, Envoy and all of the other CNCF-hosted projects.

[@vistaarjuneja8135]

Fantastic presentation!

[@danielkrajnik3817]

After lunch is the best time for the talk

[@selmison]

Excellent talk!

[@hareshkhambhadiya7041]

Awesome learning

[@kunafeh]

Wonderful talk.

[@rajendragosavi2233]

Superb Talk, Mate. Thanks

[@BiohaZd5]

Very good talk !!

[@ihuntenator]

Have to disagree, looking at the log files of docker or any container runtime is interesting, well worth learning the whole flow.

[@utpmahesh444]

suppose we are running , dev,qa and staging in same nodes but different namespaces, In that case how we implement a sidecar as a daemon set is bind to a node?

[@ak-vo8ip]

provide the .yaml file links, so that the lecture will be more helpful for understanding.

[@ithsi9544]

28:00 fluentd ecosystem

[@stepan.martyanov]

Good at fist glance, but there aren't normal multiline support. Write regexp for every next line for docker logs it's too much.

[@ithsi9544]

9:30 kube opo

[@stepan.martyanov]

nobody use -A instead of --all-namespaces