Add Request/Response Logging Middleware

[dotandev]

Add optional verbosity for debugging RPC calls by implementing a logging middleware for requests and responses.

[drips-wave]

This issue has been added to the Stellar Wave Program and is worth 150 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

[ALIPHATICHYD]

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

I'd like to work on #286 Add Request/Response Logging Middleware because RPC debugging is painful without request/response traces—logging middleware makes troubleshooting connectivity, payloads, and failures dramatically easier.

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

[edehvictor]

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

Hi maintainers,
I would like to handle this issue. I can implement the Request/Response Logging Middleware, adding the necessary observability for debugging RPC calls while ensuring performance and security best practices are met.
Implementation Plan:

• Middleware Logic: I will implement a wrapper/interceptor that captures the start time of incoming RPC requests. It will log the method name and input parameters (request body) immediately.
• Response Hook: I will tap into the response stream (or promise resolution) to log the execution duration, status code/error, and the final response payload upon completion.
• Configuration: I will add an optional verbosity flag (e.g., via environment variables or a config object) to toggle these logs on/off, ensuring production logs remain clean unless debugging is required.
• Sanitization: I will implement a basic masking utility to ensure sensitive fields (like passwords or tokens) are redacted from the logs before outputting.

I am ready to start immediately.

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

[codeZe-us]

@codeZe-us has applied to work on this issue as part of the Stellar Wave Program's 1st wave.

I can get this done

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

[codeZe-us]

@codeZe-us has applied to work on this issue as part of the Stellar Wave Program's 1st wave.

I can get this done

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

[DanielEmmanuel1]

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

Can I take on this issue please

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

[DanielEmmanuel1]

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

Can I take on this issue please

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

[DanielEmmanuel1]

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

Can I take on this issue please

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

[drips-wave]

Congratulations, @edehvictor! 🎉 Your application was accepted by the repo's maintainers, and the issue is due on January 31, 2026.

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

[drips-wave]

Congratulations, @edehvictor! 🎉 Your application was accepted by the repo's maintainers, and the issue is due on January 31, 2026.

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

[sublime247]

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

Hi
I would like to resolve this issues

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