[Enhancement] Add structured correlation IDs to API requests for distributed tracing

[RUKAYAT-CODER]

Overview

API requests lack correlation IDs, making it impossible to trace a user action across multiple service calls in server logs. When a user reports a bug that requires analyzing 'what happened when I enrolled in course X', engineers must manually cross-reference timestamps across multiple log streams. A per-request UUID sent as X-Request-ID header enables instant log correlation.

Specifications

Features:

• X-Request-ID header generated per API request (uuid v4)
• Request ID included in all appLogger entries made during the request lifecycle
• Request ID passed to Sentry context on error events
• Server echoes X-Request-ID in response; client logs both sent and received IDs

Tasks:

• In axios.config.ts request interceptor, generate UUID and set headers['X-Request-ID']
• Store request ID in logContext via pushLogContext({ requestId })
• In response interceptor, read echo'd header and log if different from sent (proxy stripping check)
• Pop log context in response interceptor cleanup
• Add unit test confirming X-Request-ID header present on all requests

Impacted Files:

• src/services/api/axios.config.ts
• src/config/logging.ts

Acceptance Criteria

• Every API request carries unique X-Request-ID header
• Request ID appears in all appLogger entries within the request lifecycle
• Sentry error events include requestId in extra context
• Unit test confirms UUID format and presence on all outbound requests

[Oluwasuyi-Timilehin]

@Oluwasuyi-Timilehin has applied to work on this issue as part of the Stellar Wave Program's 6th wave.

Hey Maintainer, I have gone through the details of the issue and i am capable of resolving it, I would love to be assigned to work on it ASAP.please assign me!!
ETA: 2 hours

ℹ️ Repo Maintainers: To accept this application, review their application or assign @Oluwasuyi-Timilehin to this issue.

[ayshadogo]

@ayshadogo has applied to work on this issue as part of the Stellar Wave Program's 6th wave.

Good day

I have read the requirements of this issue and i am confident that i can solve this

ℹ️ Repo Maintainers: To accept this application, review their application or assign @ayshadogo to this issue.

[drips-wave]

Congratulations, @ayshadogo! 🎉 Your application was accepted by the repo's maintainers, and the issue is due on June 30, 2026.

🧑‍💻 @ayshadogo: Please resolve the issue such that the repo's maintainers have enough time to review your contribution before the due date. You'll earn Points for completing the issue on-time, which will make you eligible for a share of the Stellar Wave Program's reward pool.

Warning

When opening a PR, please link it to this issue to ensure it gets tracked accurately. Points are awarded when this issue is marked as completed by the maintainer.

🤠 Repo maintainers: Please keep an eye on the contributor's progress and review their work before the due date. You can manage this issue, including adjusting its complexity and points, here.

🌊 Happy Wave 🌊