What you will learn in this TP
- Install the Operator
- Declare Collector and Instrumentation
- Instrument through annotation
Introduction #
What you will learn in this section
- Install the Operator
- Declare Collector and Instrumentation
- Instrument through annotation
Context. The platform team wants every cluster application to produce traces without each team changing its images. You validate the Operator approach.
Prerequisites: Docker, kubectl and kind · Estimated time: 50 min
An application instrumented without image changes, whose spans reach an Operator-managed Collector.Hands-on #
Guided steps, with their solution.
1. Prepare the cluster
Why? The Operator uses admission webhooks whose certificates are managed by cert-manager.
Create a kind cluster, install cert-manager then the Operator, and wait until they are available.2. Declare a Collector
Why? The Collector is described as a Kubernetes resource: the Operator creates the Deployment, Service and ConfigMap.
Create ademonamespace and anOpenTelemetryCollectorresource in deployment mode with an OTLP receiver,k8sattributesand thedebugexporter.3. Declare instrumentation
Why? The Instrumentation resource centralises exporter, propagators and sampling for a whole namespace.
Create anInstrumentationresource that sends OTLP/HTTP to the Collector, with tracecontext and baggage propagators and 100% sampling.4. Instrument an application through annotation
Why? The annotation is enough: the Operator injects the Python agent at pod start, without changing the image.
Deploy a small Flask application in a standard Python image with theinstrumentation.opentelemetry.io/inject-pythonannotation, then look at the injected init container andOTEL_*variables.5. Check the spans
Why? The debug exporter prints received spans with the Kubernetes attributes added by k8sattributes.
Generate a few requests through a port-forward, then look in the Collector logs for theGET /span,service.nameandk8s.pod.name.6. Evolve and clean up
Why? Changing the Instrumentation resource only affects recreated pods: deployments must be restarted.
Set sampling to 10%, restart the deployment, check the newOTEL_TRACES_SAMPLER_ARGvalue, then delete the cluster.
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
OpenTelemetry on Kubernetes: Operator, auto-instrumentation and Collector
Deploy OpenTelemetry on Kubernetes: Collector deployment modes (DaemonSet, Deployment, sidecar, S...
OpenTelemetry: automatic vs manual instrumentation
Understand the differences between automatic and manual instrumentation with OpenTelemetry, their...
Zero-code instrumentation with Grafana Beyla (OpenTelemetry eBPF Instrumentation)
Get RED metrics and HTTP/gRPC traces from any application without changing it: Grafana Beyla and ...
Sending traces to Tempo: OpenTelemetry instrumentation and Alloy
Produce and route traces to Tempo: Python/Java/Node auto-instrumentation, the manual SDK, OTEL en...
Datadog on Kubernetes: Operator, Cluster Agent and Autodiscovery
Monitor Kubernetes with Datadog: the Datadog Operator and the DatadogAgent resource, Cluster Agen...
Instrumenting applications for Jaeger with OpenTelemetry
Send traces to Jaeger with OpenTelemetry: auto-instrumentation (Java, Python, Node.js), SDK and m...
OpenInference: the OpenTelemetry conventions for tracing AI applications
Detailed guide to OpenInference: OpenTelemetry semantic conventions and instrumentations for LLMs...
Core OpenTelemetry concepts: signals, resources, context and maturity
The essential OpenTelemetry vocabulary: the four signals, API and SDK, resource and instrumentati...
OpenTelemetry (OTel) best practices: the guide to modern observability
Master OpenTelemetry with our expert advice: implementing the Collector, following semantic conve...