When Things Go Sideways: Troubleshooting the OTel Operator
Talkat Observability Day North America 2024 · on Tuesday, 2024-11-12· at 10:40· Salt Palace | Level 2 | 255 B·
summary
Covers concrete installation and troubleshooting steps for the OpenTelemetry Operator: Kubernetes >=1.23, install cert-manager (or provision TLS) before the operator, install via kubectl or Helm, and wait for cert-manager to finish. Explains Collector CR differences (V1beta1 vs v1alpha1), deployment modes (sidecar, daemonset, deployment, statefulset), and how config maps, service names and ports (use 4318 for HTTP/python; sidecar must use localhost) interact. Auto-instrumentation requires an Instrumentation CR deployed before the app, the annotation in pod template metadata (e.g. inject-python), check init containers, kubectl events and operator logs to debug.
AI-written summary · about
chapters (10)
- 0:00Introduction
- 1:24Conference overview
- 2:06OpenTelemetry Operator
- 3:11Installing the Operator
- 4:13Deploying the Collector
- 5:56Troubleshooting Collector deployment
- 10:09Auto instrumentation
- 15:50Auto instrumentation pitfalls
- 21:32Key takeaways
- 22:57Resources
related talks
28mThe Daemonset in the Details: Pitfalls of OpenTelemetry Collector Deployments
34mKubernetes Observability with OpenTelemetry
50mGuide to Observability with OpenTelemetry
26mWelcome to the OTEL California
25mOpenTelemetry Collector Deployment Patterns
30mOpenTelemetry 101
27mTop 5 Things to Know Running OpenTelemetry on Kubernetes
25mOpenTelemetry for Platform Engineers: Paving the Road To Self-Service Observability