The Unexplored World of OpenTelemetry and Service Mesh
Talkat OTel Community Day North America 2022 · on Monday, 2022-06-20· at 11:05· 303+304, JW Marriott Austin | 110 E 2nd St·
summary
Service mesh can emit spans without context but that produces broken traces unless services themselves implement OpenTelemetry and propagate W3C headers; mesh spans add useful routing-level metadata (which version served a request, proxy-auth decisions) and reveal auth or retry behavior, but they raise storage/processing cost by adding extra spans, break common head sampling approaches because the mesh samples before the app, and introduce protocol mismatches (Envoy/meshes lacking OTLP or using B3) that require coordination and config changes.
AI-written summary · about
chapters (8)
- 0:00Start
- 5:37Open Telemetry Distro?
- 6:08Service Mesh in traces
- 7:24Trace example - with mesh telemetry
- 9:22Service Mesh magic
- 10:16Trace example - without mesh telemetry
- 11:48Installation options
- 17:26Takeaway
related talks
20mKeynote: Service Meshes and Observability
22mBridging the OpenTelemetry Adoption Gap in Cloud-Native Applications
20mService Mesh: A Hole in the Pocket?
07mGetting the most out of service mesh
32mDisintegrated telemetry: The pains of monitoring asynchronous workflows
46mThe State of OpenTelemetry
11mWelcome & Opening Remarks
27mEnd-to-end visibility in the cloud w/OpenTelemetry