Observability Injection: Distributed Tracing via Sidecars
Overview
What this challenge is about.
Enable Envoy tracing with the OpenTelemetry tracer in Istio MeshConfig. Configure a Tempo backend with a Grafana frontend. Verify W3C tracecontext propagation across all 26 services (some are legacy and may drop headers — list them and recommend a header-preservation fix). Identify the 6 services with the most weekly changes; add in-process spans there using OpenTelemetry SDKs for richer business-level attributes. Deliver Istio + collector + Tempo configurations, a per-service tracing-coverage report, the prioritized in-process-span backlog, and a 6-page methodology memo.
The Brief
What you'll do, and what you'll demonstrate.
Use service-mesh-injected sidecars to deliver baseline distributed tracing across 26 services without code changes, and identify the 6 services that warrant in-process span instrumentation.
Earning criteria — what you'll demonstrate
- Configure Envoy + Istio to emit OpenTelemetry-compatible spans
- Reason about W3C tracecontext propagation through mixed-stack services
- Decide where in-process spans add value beyond sidecar-injected spans
- Plan observability investment based on change frequency, not service count
Program Fit
Where this fits in your program.
Sharpens the same skills your degree expects you to demonstrate.
Skills
Skills you'll demonstrate.
Each one shows up on your verified credential.
Careers
Roles this prepares you for.
Real titles. Real skill bridges. Pick the one closest to your trajectory.
Career mappings coming soon.