Introducing Logs in OpenTelemetry: What It Unlocks and How to Use It - Morgan McLean & Dan Jaglowski

Don't miss out! Join us at our next Flagship Conference: KubeCon + CloudNativeCon Europe in Paris from March 19-22, 2024. Connect with our current graduated, incubating, and sandbox projects as the community gathers to further the education and advancement of cloud native computing. Learn more at kubecon.io
Introducing Logs in OpenTelemetry: What It Unlocks and How to Use It - Morgan McLean, Splunk & Dan Jaglowski, observIQ
Logs have just become a first-class signal in OpenTelemetry, meaning that the Collector and APIs / SDKs can capture, decorate, pre-process, and export logs alongside metrics and traces to any backend for storage and analytics. These capabilities offer substantial benefits and are now ready for production usage, and it’s the best possible time to get started. In this session, you will learn from two people who initiated and defined much of OpenTelemetry’s logging capabilities: - Why logging in OpenTelemetry matters and why we added it - How logs benefit from OpenTelemetry’s consistent and enforced semantic conventions - A live demonstration of the two paths for capturing logs in OpenTelemetry: capturing logs in-process, and from existing file sources - A live demonstration of pre-processing logs in the Collector, showing the power of cross-signal processing with features like trace-based log sampling - Real-world examples from end-user firms already relying on this in production

[@ivannpaz]

So, is there any response out there regarding that very last question on how to not sample logs at all? (if needed, of course)

[@lhxperimental]

Guy wearing coat sounds like Elon Musk

[@user-mo4wq6gl9p]

haha I thought of this too the moment he started.