X'inhu distributed tracing u kif jaħdmu correlation IDs?

Question

IT Interview Practice · Accepted Answer

**Distributed tracing** isegwi singola riċesta hekk kif tivvjaġġa fuq ħafna servizzi, sabiex tara l-passaġġ sħiħ end-to-end u issib fejn jseħħ latenza jew iżbalji. **Correlation/trace ID** jirbatt flimkien l-ispans kollha ta' riċesta waħda.

## Kif taħdem

L-ewwel servizz jiġġenera **trace ID**; kull sejħa downstream tippropagaha (u l-parent **span ID**) fl-headers.

```http
GET /checkout HTTP/1.1
traceparent: 00-4bf92f3577b34da6a3ce929d0e0e4736-00f067aa0ba902b7-01
# trace-id ───────────────────────────^   ^── span-id
```

```text
Trace abc123:
  Gateway      ├──────────────────────────────┤ 220ms
   Orders        ├────────────┤ 90ms
    Payments        ├──────┤ 60ms   ← slow span found here
    Inventory       ├──┤ 15ms
```

## X'tagħtik

- **Latency breakdown** — liema servizz/span hija bil-qluf.
- **Error localization** — liema hop falliet.
- **Dependency map** — x'attwalment jidda fejn.

Altri: OpenTelemetry (instrumentation), Jaeger / Zipkin (storage + UI).

## Pitfalls

```text
⚠️ If one service drops the trace header, the trace breaks
⚠️ 100% sampling is expensive — sample, but keep errors
⚠️ Logs are useless across services without the correlation ID attached
```

## Għaliex hija importanti

Bla tracing, id-debugging ta' riċesta bil-qluf jew li falliet fuq munzelli ta' servizzi hija biss taħdita; magħha, tara eżattament liema hop hu responsabbli.

L-ipropagazzjoni ta' correlation ID minn kull linja log u sejħa hija l-ikbar investiment ta' observabilità b'leverage għoli f'sistema ta' microservices.

Kif taħdem

X'tagħtik

Pitfalls

Għaliex hija importanti

Mistoqsijiet relatati