Overview
OpenTelemetry is initialised in both frontend and backend but trace IDs are not propagated across HTTP calls. This means a single user action cannot be traced across services in Jaeger/Zipkin.
Specifications
Tasks:
- Add W3C raceparent header injection in the frontend API client (lib/api/client.ts)
- Configure backend OTEL SDK to extract incoming raceparents
- Verify end-to-end trace in local Jaeger
Impacted Files:
- FrontEnd/my-app/lib/api/client.ts
n- BackEnd/src/config/opentelemetry.config.tsn
Acceptance Criteria:
- Single user action produces a linked trace spanning frontend ? backend
Overview
OpenTelemetry is initialised in both frontend and backend but trace IDs are not propagated across HTTP calls. This means a single user action cannot be traced across services in Jaeger/Zipkin.
Specifications
Tasks:
Impacted Files:
n- BackEnd/src/config/opentelemetry.config.tsnAcceptance Criteria: