Distributed Tracing Integration with OpenTelemetry and Knative
summary
Shows how OpenTelemetry + Knative capture end-to-end traces from a Quarkus Java app into Jaeger while scaling to zero on OpenShift. Demo instruments a service with an OpenTelemetry dependency, records ~13 local traces, a DB span at 135 μs, cluster response at 1.75 ms, and survives a thousand-concurrent request spike that spawns hundreds of pods. Collector centralizes traces so you can map requests to specific pods and code spans even after pods terminate.
AI-written summary · about
chapters (14)
- 0:00Distributed tracing intro
- 3:59Three pillars of observability
- 7:08OpenTelemetry as standard
- 10:20OpenTelemetry components
- 12:04Serverless apps with Knative
- 13:48Quarkus for cloud-native
- 15:53Live demo setup
- 17:59Local tracing with Jaeger
- 20:07Deploy to Kubernetes
- 23:20Serverless auto-scaling
- 24:46Tracing in Knative
- 26:11Stress testing demo
- 27:58Summary and resources
- 28:43Q&A
related talks
28mDistributed Tracing Integration with OpenTelemetry and Knative _ _ _
45mDistributed Tracing Integration with OpenTelemetry and Knative
42mDistributed Tracing Integration with OpenTelemetry and Knative
40mDistributed Tracing Integration with OpenTelemetry and Knative
34mDistributed Tracing Integration with OpenTelemetry and Knative
50mI'm Tracing you!
39mThe Hidden Gems of Distributed Tracing
08mOpenTelemetry and Quarkus