Implement structured logging with request correlation IDs (#16)

[Kirtiman-55]

#16

Summary

This PR adds structured logging with request correlation IDs so API, orchestrator, and payment logs can be traced end-to-end.

What changed

• Added a structured logger (src/logger.js) with:
  • JSON mode (default)
  • optional pretty mode for local readability
• Added request correlation middleware behavior:
  • reuses incoming x-correlation-id / x-request-id when provided
  • generates ID if missing
  • returns x-correlation-id in response headers
• Added request lifecycle logs:
  • request_start
  • request_complete
  • request_error
• Added correlation-aware orchestrator/payment logs with relevant fields:
  • agentId
  • paymentMethod
  • txHash
• Updated rate limiter logging to use structured logger with correlation IDs
• Added logging config/docs:
  • LOG_FORMAT=json|pretty

Acceptance Criteria

• Every API request has a correlation ID: ✅
• Payment/orchestrator logs traceable end-to-end: ✅
• Log format works in local and CI environments: ✅

Validation

• npm test passes

[vercel]

@Kirtiman-55 is attempting to deploy a commit to the flamki's projects Team on Vercel.

A member of the Team first needs to authorize it.

[drips-wave]

Hey @Kirtiman-55! 👋 It looks like this PR isn't linked to any issue.

If this PR is for one of the issues assigned to you as part of a Wave, please link it to ensure your contribution is tracked properly. You can do this by adding a keyword to the PR description (e.g., Closes #123), or by clicking a button below:

Issue	Title
#16	Implement structured logging with request correlation IDs	Link to this issue
#31	Stop printing wallet secrets in setup output by default	Link to this issue
#22	Add timeout and retry controls for Anthropic API calls	Link to this issue
#18	Add integration tests for x402 premium endpoints	Link to this issue

ℹ️ Learn more about linking PRs to issues

[coderabbitai]

Warning

Review limit reached

@Kirtiman-55, we couldn't start this review because you've reached your PR review rate limit.

More reviews will be available in 44 minutes and 28 seconds. Learn how PR review limits work.

Your organization has run out of usage credits. Purchase more in the billing tab.

⌛ How to resolve this issue?

After more reviews become available, a review can be triggered using the @coderabbitai review command as a PR comment. Alternatively, push new commits to this PR.

We recommend that you space out your commits to avoid hitting the rate limit.

🚦 How do rate limits work?

CodeRabbit enforces hourly rate limits for each developer per organization.

Our paid plans include higher PR review limits than trial, open-source, and free plans. In all cases, reviews become available again over time. During sustained high-volume PR review activity, CodeRabbit may temporarily slow when the next review becomes available.

Please see our Fair Usage Limits Policy for further information.

ℹ️ Review info

⚙️ Run configuration

Configuration used: defaults

Review profile: CHILL

Plan: Pro

Run ID: 9a8990bb-8cf5-4e48-b962-ccc052f2919c

📥 Commits

Reviewing files that changed from the base of the PR and between b9a790d and 7754cab.

📒 Files selected for processing (8)

• .env.example
• README.md
• src/agents/orchestrator.js
• src/config.js
• src/logger.js
• src/middleware/errorHandler.js
• src/middleware/rateLimiter.js
• src/server.js

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands and usage tips.}