Menene Distributed Tracing kuma ta yaya Correlation IDs suke aiki?

Question

Accepted Answer

**Distributed tracing** yana bin bukatun gida ɗaya yayin da ya tashi a kan ayyukan da yawa, don kada ka ga hanya daga ƙarshe zuwa ƙarshe kuma nemi inda jinkirin ko kurakuran suke faruwa. A **Correlation/trace ID** yana daura spans duka na bukatun gida ɗaya tare.

## Ta yaya ya aiki

Aikin farko yana bubuwa **trace ID**; kowane karaya da ke gida yana yada shi (da uba **span ID**) a sirinkai.

```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
```

## Abin da ya ba ka

- **Jinkirin riko** — aikin/span wace a jira.
- **Saita kurakuran** — wane san ya gazawa.
- **Taswirar dogaro** — abin da ya kira gida.

Kayaye: OpenTelemetry (na aiki), Jaeger / Zipkin (ajiya + UI).

## Haɗin gidaje

```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
```

## Yaushe ya zama mahimmanci

Ba tare da tracing ba, aikatarwa bukatun gida a slo ko gazawa a zaɓe ayyuka ba sanɗiyya ne; tare da shi, ka ga gaida wane san ya zama laifi.

Yada ID-adadi ta kowane layin kidaya da karaya shine babbar jajirre na illantar mafi gaske a tsarin microservices.