Request logger: correlation ID propagation

[1nonlypiece]

Description

Accept X-Request-Id or generate; propagate.

Requirements and context

• Tests

• Must be secure, tested, and aligned with existing Express + TypeScript patterns

• Should be observable (logging/metrics where appropriate) without leaking PII

Suggested execution

1. Fork the repository and create a branch: git checkout -b feature/correlation-id
2. Implement changes in Disciplr-backend only (no frontend / contracts in this issue)

Implement

• requestLogger.ts

Tests and documentation

• Extend or add Jest / tsx --test suites as appropriate
• Run: npm test
• Update inline comments or existing docs under Disciplr-backend/docs only if the feature needs it (no unsolicited new markdown files)

Test and commit

1. Run tests with coverage if configured; cover edge cases listed in requirements
2. Paste summarized test output in the PR
3. Note any security or data-handling implications

Example commit message

feat(logging): request correlation ids

Guidelines

Item	Target
Test coverage	≥ 95% on new/changed backend code where feasible
API contracts	Stable JSON shapes; document breaking changes in PR
Timeframe	96 hours from assignment

[drips-wave]

This issue has been added to the Stellar Wave Program and is worth 200 Points.

🧑‍💻 Interested in contributing? Apply to work on this issue on Drips Wave, earn points, and receive rewards.

Warning

Only applications submitted via the apply link above will be considered. Please do not apply by commenting on the issue or opening a PR directly.

🤠 Repo maintainers: You can manage this issue's Points and Complexity on your Maintainer Dashboard here. Please keep an eye on applications and respond quickly 💙

ℹ️ Learn more about Drips Wave

[devxsameer]

@devxsameer has applied to work on this issue as part of the Stellar Wave Program's 3rd wave.

I’d like to take this issue. I’m a backend-leaning full stack developer with experience in logging and observability, and I can implement correlation ID propagation by accepting or generating X-Request-Id, wiring it through middleware, and ensuring it’s consistently available for logging without exposing sensitive data.

ETA: 2–3 hours.

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

[drips-wave]

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

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