Why Distributed tracing in HLD? - Purpose & Use Cases

The Big Idea

What if you could instantly see exactly where your system slows down, like a GPS for your code?

The Scenario

Imagine you run a busy restaurant with many chefs and waiters. When a customer complains about a slow order, you try to find where the delay happened by asking each person individually. It takes a lot of time and you often get confused answers.

The Problem

Manually tracking requests across many services is slow and confusing. You miss important details, blame the wrong team, and fixing issues takes forever. Without clear visibility, problems hide in the chaos.

The Solution

Distributed tracing acts like a smart tracker that follows each customer order through every step in the kitchen and dining area. It collects clear, connected information so you see exactly where delays or errors happen, making troubleshooting fast and accurate.

Before vs After

✗ Before

Log each service separately and guess the flow

✓ After

Use distributed tracing to link logs with unique trace IDs

What It Enables

Distributed tracing lets you see the full journey of a request across all services, unlocking fast problem detection and smoother system performance.

Real Life Example

When an online shopper faces a slow checkout, distributed tracing helps engineers quickly find if the delay is in payment processing, inventory check, or shipping calculation.

Key Takeaways

Manual tracking is slow and error-prone in complex systems.

Distributed tracing connects all parts of a request for clear visibility.

This leads to faster debugging and better user experience.

Practice

1. What is the main purpose of distributed tracing in a system?
TraceID and spans are used to:

easy

A. Balance load between servers automatically

B. Store user data securely in a database

C. Track requests as they move through multiple services

D. Encrypt communication between clients and servers

Solution

1. Step 1: Understand distributed tracing basics

   Distributed tracing helps track how a request flows through different parts of a system.

2. Step 2: Identify the role of TraceID and spans

   TraceID links all parts of a request, and spans represent each step or service involved.

3. Final Answer:

   Track requests as they move through multiple services -> Option C

4. Quick Check:

   Distributed tracing = Track requests [OK]

Hint: TraceID connects steps in request flow [OK]

Common Mistakes:

• Confusing tracing with data storage
• Mixing tracing with load balancing
• Thinking tracing encrypts data

2. Which of the following is the correct way to represent a span in distributed tracing data?

easy

A. "traceId:abc123;spanId:xyz789;operation:db_query"

B. { "traceId": "abc123", "spanId": "xyz789", "operation": "db_query" }

C. [ "traceId", "spanId", "operation" ]

D. abc123xyz789

Solution

1. Step 1: Identify correct data format for spans

   Spans are usually represented as structured data like JSON objects with keys and values.

2. Step 2: Compare options

   { "traceId": "abc123", "spanId": "xyz789", "operation": "db_query" } shows a JSON object with clear keys for traceId, spanId, and operation, which is standard.

3. Final Answer:

   { "traceId": "abc123", "spanId": "xyz789", "operation": "db_query" } -> Option B

4. Quick Check:

   Span = JSON object with keys [OK]

Hint: Spans use JSON key-value pairs [OK]

Common Mistakes:

• Using arrays instead of objects
• Using plain strings without structure
• Using XML tags incorrectly

3. Given the following trace data snippet:

{"traceId": "t1", "spans": [{"spanId": "s1", "parentId": null, "operation": "frontend"}, {"spanId": "s2", "parentId": "s1", "operation": "backend"}, {"spanId": "s3", "parentId": "s2", "operation": "db_query"}]}

What is the correct order of operations for this request?

medium

A. frontend -> backend -> db_query

B. db_query -> backend -> frontend

C. backend -> frontend -> db_query

D. frontend -> db_query -> backend

Solution

1. Step 1: Analyze parent-child relationships

   The span with parentId null is the root: frontend (s1). Backend (s2) is child of frontend, and db_query (s3) is child of backend.

2. Step 2: Determine operation order

   Request flows from frontend to backend to db_query following parent-child links.

3. Final Answer:

   frontend -> backend -> db_query -> Option A

4. Quick Check:

   Parent-child order = frontend to db_query [OK]

Hint: Follow parentId links from root span [OK]

Common Mistakes:

• Ignoring parentId null as root
• Reversing operation order
• Mixing span order in array with execution order

4. You notice that some spans in your distributed tracing system have missing traceId values. What is the most likely cause?

medium

A. The tracing library failed to propagate the traceId across services

B. The database storing traces is full

C. The network is too slow to send trace data

D. The user did not authenticate properly

Solution

1. Step 1: Understand traceId propagation

   TraceId must be passed along all services handling the request to link spans correctly.

2. Step 2: Identify cause of missing traceId

   If traceId is missing, it usually means the tracing library or instrumentation did not forward it properly.

3. Final Answer:

   The tracing library failed to propagate the traceId across services -> Option A

4. Quick Check:

   Missing traceId = propagation failure [OK]

Hint: Missing traceId means propagation error [OK]

Common Mistakes:

• Blaming storage or network issues
• Confusing authentication with tracing
• Assuming traceId is optional

5. You want to design a distributed tracing system for a microservices architecture with hundreds of services. Which approach best ensures scalability and minimal overhead?

hard

A. Store all trace data locally on each service without aggregation

B. Trace every request fully and store all spans in a single centralized database

C. Send trace data synchronously during each request to avoid data loss

D. Use sampling to trace only a subset of requests and store spans in a scalable backend

Solution

1. Step 1: Consider scalability challenges

   Tracing every request fully creates huge data and overhead, which is not scalable for hundreds of services.

2. Step 2: Evaluate best practices

   Sampling reduces data volume by tracing only some requests, and scalable backends handle storage efficiently.

3. Step 3: Assess other options

   Synchronous sending blocks requests, and local storage prevents global analysis.

4. Final Answer:

   Use sampling to trace only a subset of requests and store spans in a scalable backend -> Option D

5. Quick Check:

   Sampling + scalable storage = scalable tracing [OK]

Hint: Sample requests to reduce tracing load [OK]

Common Mistakes:

• Tracing all requests causing overload
• Synchronous sending blocking services
• Not aggregating trace data centrally