Add request ID middleware and correlate logs with request context

[prodbycorne]

Overview

Logs from concurrent requests are interleaved with no way to correlate them. Adding a request ID to every log line allows tracing a single request's journey through the system, essential for debugging production issues.

Current Problem

[INFO] Fetching price for XLM
[INFO] Fetching price for USDC
[ERROR] CoinGecko fetch failed
[INFO] Cache hit for XLM

Which request caused the CoinGecko failure? Impossible to tell.

Solution

1. Generate a request ID on every incoming request (nanoid or crypto.randomUUID())
2. Attach to req.id via middleware early in the chain
3. Pass to logger via async-local storage (ALS) so child log calls inherit it:

// src/middleware/requestId.js
const { AsyncLocalStorage } = require('node:async_hooks');
const requestContext = new AsyncLocalStorage();

function requestIdMiddleware(req, res, next) {
  req.id = crypto.randomUUID();
  res.setHeader('X-Request-ID', req.id);
  requestContext.run({ requestId: req.id }, next);
}

4. Update src/logger.js to include requestId from ALS in every log line:

const child = logger.child({
  requestId: requestContext.getStore()?.requestId ?? 'system'
});

After this change:

{ "level": "error", "requestId": "f8a2-...", "msg": "CoinGecko fetch failed" }
{ "level": "info",  "requestId": "a1b3-...", "msg": "Cache hit for XLM" }

Acceptance Criteria

• X-Request-ID header on every response
• Request ID propagated to all log lines within that request
• Background tasks log with requestId: 'system'
• Test: log output includes matching requestId for a given request
• ALS used (not req passed manually through every function)

[Kaycee276]

Hi maintainer, can i work on this issue?

[YfengJ]

Hi maintainers, I would like to apply for this issue if it is still available.

If assigned, I can add request ID middleware, propagate the ID into structured logs and response headers where appropriate, and include tests or examples showing request correlation without logging sensitive headers, auth tokens, or request bodies.

I will wait for maintainer or GrantFox assignment/confirmation before cloning, implementing, or opening a PR.

[clintjeff2]

Hello, I have 6 years of experience working on tasks like this and handling similar challenges across backend, frontend, and smart-contract development. I have carefully read and fully understood the task requirements, and I am confident I can deliver a clean, efficient, and well-tested solution promptly. I always ensure high-quality implementation, maintainability, and adherence to best practices.

Pull request in 5 hours.

[Jennylila]

Hello, I’ve gone through the requirements and I’m confident I can implement a proper solution that matches the acceptance criteria. Kindly assign this issue to me.

[grantfox-oss]

🦊 GrantFox — @Jennylila has been assigned to this issue as part of the Official Campaign campaign!

Next steps:

1. Open a Pull Request referencing this issue (e.g., Closes #34)
2. Your PR will be reviewed by the SmartDropLabs maintainers

Good luck! Track your progress on GrantFox.

[YfengJ]

Thanks for the update. Since this has been assigned to @Jennylila, I’ll step back and won’t work on a competing PR. Good luck with the implementation.

[grantfox-oss]

🎉 This issue has been marked as completed on GrantFox as part of the Official Campaign campaign!

@Jennylila's PR #58 was approved and merged by @prodbycorne.

🏆 @Jennylila: You earned 35 FoxPoints for this contribution! Your current tier: Explorer (83 total points). Track your full progress on GrantFox.

👏 Great work, @Jennylila! Keep contributing to SmartDropLabs.