[BACKEND] Add structured JSON logging with request IDs

[dev-fatima-24]

Priority: high

Description

The backend currently uses console.log with unstructured output. Structured JSON logging with a unique request ID per request is needed for production observability and log aggregation.

Acceptance Criteria

• Every log line is valid JSON with timestamp, level, requestId, message
• Request ID is generated per request and attached to all logs within that request
• Request ID is returned in the X-Request-ID response header
• Log level is configurable via environment variable
• Errors include stack traces in the error field

[Uche44]

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

Here's how I'd approach this problem:

I would introduce a centralized logging layer that replaces all direct console.log usage with a structured logger that outputs consistent JSON objects. Each log entry would include a timestamp, log level, requestId, message, and optional metadata such as error details or context-specific fields.

To support request tracing, I’d implement middleware that generates a unique requestId for every incoming HTTP request. That requestId would be attached to the request object and automatically injected into all logs produced during the lifecycle of that request. I’d also ensure the same requestId is returned in the X-Request-ID response header so clients can correlate backend behavior with frontend or external logs.

For error handling, I’d standardize error logs to always include stack traces in a dedicated error field while keeping the main message clean and consistent. This ensures debugging information is preserved without breaking log structure.

I’d make the log level configurable through environment variables so the system can switch between debug, info, warn, and error modes depending on deployment stage. In production, this would default to a more restrictive level to reduce noise, while still preserving critical observability.

Finally, I’d add tests to confirm requestId propagation, JSON log format validity, header injection, and correct log level filtering across different environments.

Let me handle this for you.

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

[olawale880]

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

please can i work on the issue

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

[charliechinedu19-netizen]

@charliechinedu19-netizen has applied to work on this issue as part of the Stellar Wave Program's 5th wave.

hey gm, can i work on this issue real quick please

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

[Vivian-04]

@Vivian-04 has applied to work on this issue as part of the Stellar Wave Program's 5th wave.

Hiiiiii, I would love to work on this quickly for youuuuu.

Kindly assign this to me..Thank youuuuuu!

ETA: 2-3hours

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

[olaayoade27-coder]

@olaayoade27-coder has applied to work on this issue as part of the Stellar Wave Program's 5th wave.

Hello I would like to work on this

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

[drips-wave]

Congratulations, @olaayoade27-coder! 🎉 Your application was accepted by the repo's maintainers, and the issue is due on June 2, 2026.

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