Add request ID tracing across API logs

[ogazboiz]

Join our community: https://t.me/+DOylgFv1jyJlNzM0

Description

API logs have no request correlation ID. When multiple requests are in-flight, their log entries are interleaved with no way to trace a single request's path through the system.

What Needs to Happen

• Generate a UUID request ID on each incoming request (or read X-Request-ID header if present)
• Attach the request ID to the response as X-Request-ID header
• Include the request ID in all Winston log entries for that request (use AsyncLocalStorage)
• Log: request received (method, path, request ID), response sent (status, duration, request ID)
• Include request ID in SSE event payloads for client-side correlation

Files

• backend/src/middleware/requestId.ts (create)
• backend/src/app.ts

Acceptance Criteria

• Every log line includes requestId
• X-Request-ID header present on all responses
• Client-provided X-Request-ID is echoed back if valid

[Opeyemi01-del]

@Opeyemi01-del has applied to work on this issue as part of the Stellar Wave Program's 4th wave.

I would love to work on ths issue

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

[Daniel202251]

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

I’m a smart contract and full-stack developer who turns complex ideas into secure, production-ready blockchain code.
With strong skills in Rust and Solidity, I build systems that are fast, safe, and built to last.
My experience with the Stellar SDK lets me ship real-world Web3 solutions that actually move value

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

[N-thnI]

@N-thnI has applied to work on this issue as part of the Stellar Wave Program's 4th wave.

Dear maintainer
Please assign me this issue

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

[sweetesty]

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

Hi I would Like to work on this issue

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

[WISDOM-WOKE22]

@WISDOM-WOKE22 has applied to work on this issue as part of the Stellar Wave Program's 4th wave.

Applying for this

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

[drips-wave]

Congratulations, @WISDOM-WOKE22! 🎉 Your application was accepted by the repo's maintainers, and the issue is due on April 29, 2026.

🧑‍💻 @WISDOM-WOKE22: 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 🌊