B-051 — Request ID propagation

[Junman140]

Severity: Low · Area: backend/observability · Evidence: Express middleware stack
Impact: Hard to correlate user report with logs. Fix direction: Add x-request-id middleware; log field. Acceptance check: Support can trace single request across services.

[benedict-cmd]

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

I’d love to work on this issue because request ID propagation is essential for observability, debugging, and tracing in backend systems. Without consistent request IDs across services and logs, it becomes difficult to track issues, diagnose failures, or understand request flows in a distributed system. Fixing this would significantly improve system transparency and maintainability.

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

[drips-wave]

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

🧑‍💻 @benedict-cmd: 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 🌊

[STX-Boot]

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

Kindly assign me this

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

[drips-wave]

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

🧑‍💻 @STX-Boot: 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 🌊