The Life of a Span
summary
Follows an instrumented application as an OpenTelemetry span is created by a tracer, picks up resource attributes and a traceID/spanID, gains attributes/events/errors, propagates via W3C tracecontext headers to child spans, and is queued by a BatchSpanProcessor before exporters send OTLP payloads (HTTP gRPC JSON) to a local collector which can enrich and forward to backends like Honeycomb or Jaeger. Notes that root span is typically sent last and batching reduces overhead.
AI-written summary · about
chapters (8)
- 0:00Spanley’s journey
- 1:03Birth with OpenTelemetry
- 3:33Growing with attributes
- 7:27Context propagation
- 10:00Span processing
- 12:03Exporting spans
- 13:31Legacy in telemetry
- 16:43Q&A
related talks
32mDisintegrated telemetry: The pains of monitoring asynchronous workflows
26mThe Art of Event Driven Observability with OpenTelemetry
24mObservability and instrumentation via OpenTelemetry
37mBeyond Getting Started: Using OpenTelemetry to Its Full Potential
46mThe State of OpenTelemetry
13mStart Tracing on Day Zero
24mTraces from Events: A New Way to Visualise Kubernetes Activities
22mOpen Telemetry for API Monitoring