Observability at the Edge: State of OpenTelemetry in Kubernetes Ingress Contro...
summary
Evaluation compares KGateway, Contour, Emissary, Istio gateway and Traefik using a seven‑dimension OpenTelemetry maturity model and hands‑on tests with an OpenTelemetry Collector. Key findings: OTLP traces are broadly supported and root spans are created at ingress, but semantic attributes often lag; Prometheus-native metrics remain dominant (KGateway ~140 envoy metrics, Contour ~486, Emissary ~371, Traefik ~11); access logs are structured but correlation usually requires Collector transforms; Traefik exports OTLP for traces, logs and metrics, reducing pipeline work.
AI-written summary · about
chapters (11)
- 0:00Observability at the edge
- 1:26Ingress & OpenTelemetry basics
- 5:18OpenTelemetry maturity model
- 9:14K Gateway’s OTel support
- 12:45Contour tracing & logging limits
- 15:12Traefik’s OTel-first approach
- 17:40Emissary tracing & metrics gaps
- 19:49Gateway tracing strengths
- 21:37Cross-controller OTel patterns
- 23:21OTel maturity for platform teams
- 25:09Community collaboration & wrap-up
related talks
35mBeyond “Supports OpenTelemetry”: A Maturity Model for Cloud-Native Observability
46mThe State of OpenTelemetry
34mKubernetes Observability with OpenTelemetry
46mObservability Ecosystem in Kubernetes
50mOpen Telemetry: The Rise of Open Standards in Observability
50mGuide to Observability with OpenTelemetry
25mThe Lean Observability Stack: Quick and Native Telemetry for Service...
27mTop 5 Things to Know Running OpenTelemetry on Kubernetes