Implement API Request/Response Logging Middleware

[Baskarayelu]

Description:

Add structured request/response logging for all API routes so ops can debug issues and analyze usage without logging sensitive payloads.

Requirements

• Log for each request: method, path, statusCode, durationMs, requestId (if present)
• Do not log full request body (e.g. passwords, signatures); optionally log sanitized fields (e.g. address prefix)
• Use structured format (JSON) to stdout for log aggregation
• Optional: log response body size only (no content) for large payloads
• Document log format and how to correlate via requestId

Acceptance Criteria

• Logging middleware applied to /api routes
• No secrets or full bodies in logs
• Log format documented

[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

[Favourof]

@Favourof has applied to work on this issue as part of the Stellar Wave Program's 2nd wave.

I’m Favour Omotosho, a developer focused on building observable, production-ready systems with clean operational visibility.

For this task, I would implement a centralized API logging middleware that wraps all /api routes and emits structured JSON logs to stdout. Each request log would include:

method
path
statusCode
durationMs
requestId (from header or generated)
Optional: response body size (not content)

The middleware would measure execution time, attach or propagate a requestId for correlation, and ensure no sensitive data is logged. Full request bodies (passwords, signatures, tokens) would be excluded, with optional sanitized fields such as wallet address prefixes when necessary.

I would also document the log schema and explain how to correlate logs via requestId, ensuring compatibility with log aggregation tools and production monitoring systems.

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

[OluRemiFour]

@OluRemiFour has applied to work on this issue as part of the Stellar Wave Program's 2nd wave.

Based on your request, i will Add structured request/response logging for all API routes so ops can debug issues and analyze usage without logging sensitive payloads - according to the requirement to match the Acceptance Criteria.

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

[jahrulezfrancis]

@jahrulezfrancis has applied to work on this issue as part of the Stellar Wave Program's 2nd wave.

I'd love to work on implementing API Request/Response Logging Middleware.

I'll add structured JSON logging for all API routes that captures method, path, statusCode, durationMs, and requestId—without logging sensitive payloads. I'll ensure request bodies are sanitized (e.g., no passwords) and document the log format for easy correlation via requestId.

ETA: ~3 hours.

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

[caxtonacollins]

@caxtonacollins has applied to work on this issue as part of the Stellar Wave Program's 2nd wave.

Hi 👋 am a full-stack developer
I will love to work on this issue please assign

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

[Georgebingi]

@Georgebingi has applied to work on this issue as part of the Stellar Wave Program's 2nd wave.

Hi my name is George and I'm a full stack develop I'll like to work on this issue because It picks my interest and Ive got experience with similar projects I'll have it solved in 24 hours or less

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

[1sraeliteX]

@1sraeliteX has applied to work on this issue as part of the Stellar Wave Program's 2nd wave.

I would like to work on this issue because structured API logging is essential for observability and debugging without leaking sensitive data. I can implement middleware to log method, path, status, duration, and requestId in JSON, sanitize payloads, optionally log response size, and document the log format and correlation strategy.

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

[Mrwicks00]

I will deliver this issue to you in few hours, assign this issue to me, Thanks in advance

[Miracle656]

@Miracle656 has applied to work on this issue as part of the Stellar Wave Program's 2nd wave.

Hey team 👋

I'd like to work on this!

My plan:

• lib/middleware/logger.ts emitting structured JSON to stdout: requestId, method, path, statusCode, durationMs, responseSizeBytes, timestamp
• Never log full request body — strip passwords, auth headers, signatures
• Optionally log sanitized fields (e.g. address prefix only)
• Applied to all app/api/ routes via Next.js middleware or route wrapper
• README documenting log format and requestId correlation

Quick questions:

• Preferred logger (pino, winston, or plain console.log)?
• Generate requestId server-side if missing from headers?
• Any specific log aggregation format required?

Estimated delivery: 2–3 days from assignment. Please assign it to me 🙌

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

[drips-wave]

Congratulations, @1sraeliteX! 🎉 Your application was accepted by the repo's maintainers, and the issue is due on February 26, 2026.

🧑‍💻 @1sraeliteX: 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 issued 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 🌊