Interview kitsBlog

Your dream job? Lets Git IT.
Interactive technical interview preparation platform designed for modern developers.

XGitHub

Platform

  • Categories

Resources

  • Blog
  • About the app
  • FAQ
  • Feedback

Legal

  • Privacy Policy
  • Terms of Service

© 2026 LetsGit.IT. All rights reserved.

LetsGit.IT/Categories/Observability
Observabilitymedium

What is distributed tracing and how do you propagate context?

Tags
#tracing#context#distributed-systems
Back to categoryPractice quiz

Answer

Distributed tracing tracks a request across services using trace/span IDs. Context is propagated via headers (e.g., W3C traceparent) or messaging metadata so every service can attach spans to the same trace.

Advanced answer

Deep dive

Tracing links work units across boundaries:

  • Trace = end-to-end request; span = timed unit of work.
  • Propagate context through HTTP headers or message brokers.
  • Use consistent sampling strategy across services.
  • Correlate traces with logs via trace_id.

Examples

W3C traceparent header:

traceparent: 00-4bf92f3577b34da6a3ce929d0e0e4736-00f067aa0ba902b7-01

Common pitfalls

  • Missing propagation in async jobs or queues.
  • Sampling at the edge but not downstream (broken traces).
  • Creating new trace IDs in each service.

Interview follow-ups

  • How do you trace background jobs?
  • What is baggage and when would you use it?
  • How do you link traces with logs and metrics?

Related questions

Observability
How do you investigate a latency regression in production?
#latency#incident#tracing
Observability
What is sampling in tracing and what are the trade-offs?
#tracing#sampling#cost
Observability
Logs vs metrics vs traces — when do you use each?
#observability#logs
#metrics