OpenTelemetry for Logging
summary
Shows how to get logs into OpenTelemetry so logs carry trace IDs for one-click correlation, using Java (SLF4J + Logback), the OpenTelemetry Java agent, OTel Collector and an Elastic backend. Implements three concrete paths: direct OTLP appender (sends log events over gRPC, no local file), file + collector (structured JSON file parsed by the Collector), and ECS + Filebeat (Elastic Common Schema file consumed by Filebeat skipping OTLP). Demo sends ~50 documents to Elastic and correlation works, but direct OTLP risks losing local files and logging support is still early outside Java.
AI-written summary · about
chapters (12)
- 0:00Introduction to OpenTelemetry logging
- 1:23Why OpenTelemetry for logs
- 2:49Unified signal routing with OTLP
- 4:15Correlating logs with traces and metrics
- 8:07Three approaches to log integration
- 12:00Current maturity of OpenTelemetry logging
- 14:33First approach: Direct OTLP logging
- 21:24Second approach: Log file with collector
- 24:56Third approach: ECS format with Filebeat
- 30:18Correlating traces and logs demo
- 32:13Choosing the right approach
- 33:39Future outlook and Q&A
related talks
32mOpenTelemetry feat. logs, metrics and traces
41mIntroducing logs in OpenTelemetry: Features and opportunities
49mDistributed Tracing in Java? OpenTelemetry for the Rescue!
49mOpenTelemetry for Java Developers
36mObservability For You and Me with OpenTelemetry
28mGetting Started with OpenTelemetry
27mLog Support in OpenTelemetry
46mThe State of OpenTelemetry