What you will learn in this TP
- Connect an existing logger to OpenTelemetry
- Correlate logs and traces
- Collect files with filelog
Introduction #
What you will learn in this section
- Connect an existing logger to OpenTelemetry
- Correlate logs and traces
- Collect files with filelog
Context. Billing logs are text files nobody links to traces. You connect the modern service to OpenTelemetry and collect the legacy application's logs without changing it.
Prerequisites: Docker and Python 3.10 or later; the grafana/otel-lgtm stack (Collector, Tempo, Loki, Prometheus, Pyroscope and Grafana in one container) · Estimated time: 45 min
Hands-on #
Guided steps, with their solution.
1. Start the observability stack
Why? A single image provides an OTLP Collector and every backend: focus on the signal.
Startgrafana/otel-lgtm, create a Python environment and point exporters to OTLP/HTTP port 4318.2. Connect the logging module
Why? The LoggingHandler turns each logging call into an OpenTelemetry LogRecord, with the active trace context.
Writefacturation.py: a LoggerProvider with OTLP exporter, a handler added to the root logger, a TracerProvider, and INFO and ERROR logs emitted inside spans.3. Query and correlate in Grafana
Why? The trace_id carried by each log lets you jump from the log to the trace and back.
In Explore > Loki, show the service's errors, expand a line and spottrace_id,span_id, severity and your attributes. Open the linked trace, then from a Tempo span show its logs.4. Collect a legacy application's logs
Why? Without touching code, the filelog receiver reads files and parses JSON, severity and trace context.
Generate a JSON log file, then run a contrib Collector on the same network as the stack, withfilelog,json_parser,trace_parserand aresourceprocessor settingservice.name.5. Reduce and mask
Why? The Collector removes noise and personal data before storage.
Add afilterprocessor dropping INFO logs and atransformmasking e-mail addresses in the body, then check in Loki.
Difficulty level : ●●●○○ (3/5)
My progress
Sign in to track your progress and take notes. Sign in
💬 Recent discussions about this course
- Quels attributs utiliser pour nommer mes spans HTTP (semconv) ?✓ solved · 1 reply(ies)
- OpenTelemetry Collector : mes traces arrivent mais pas mes métriques✓ solved · 2 reply(ies)
Ask a question about this lesson →See all discussions about this course
Recommended Articles
Logs with OpenTelemetry: data model, appenders, correlation and collection
Master the log signal: the LogRecord data model, the Logs Bridge API and appenders (Logback, Log4...
Correlating traces, metrics, logs and profiles with OpenTelemetry
Link the four signals to diagnose quickly: shared resource, trace_id in logs, exemplars on metric...
Ingesting OpenTelemetry logs into Elasticsearch
Collect and structure logs with the OpenTelemetry Collector (filelog receiver, operators, transfo...
Capstone project: the four signals of the OpenTelemetry Demo in the Grafana stack
A capstone project spanning the observability courses: deploy the OpenTelemetry Demo, send metric...
OpenTelemetry: automatic vs manual instrumentation
Understand the differences between automatic and manual instrumentation with OpenTelemetry, their...
Sending telemetry to ClickStack: OpenTelemetry SDKs, collectors, logs, Kubernetes and browser sessions
Feeding ClickStack: ingestion key, OpenTelemetry SDK variables, forwarding through an existing co...
Collecting logs into Loki: Alloy, Promtail, Docker and OpenTelemetry
Send logs to Loki: Grafana Alloy, Promtail, the Docker driver, OTLP, good labels, parsing and enr...
Profiles, OpenTelemetry's fourth signal: continuous profiling and correlation with traces
Understand OpenTelemetry's new profile signal: continuous profiling, flame graphs, data model and...
OpenTelemetry Collector: exporters (sending telemetry to backends)
Configure OpenTelemetry Collector exporters: OTLP gRPC/HTTP, Prometheus, prometheusremotewrite, L...