[DevOps] Centralized Structured JSON Logging Implementation

[AlAfiz]

Description: Refactor the API's global logging architecture to output strictly formatted JSON strings rather than raw console text, preparing the application for ingestion by centralized monitoring tools like AWS CloudWatch or the ELK stack.
Context / Motivation: Standard console.log is useless at scale. When troubleshooting production issues across load-balanced containers, we need structured metadata (timestamps, request IDs, log levels) to filter and query logs effectively.
Acceptance Criteria: - [ ] Replace all standard console calls with a high-performance logging library like Pino or Winston.

• Ensure all logs output in a flat JSON format (e.g., {"level":"info","time":167890,"msg":"...","reqId":"xyz"}).
• Implement an Express middleware that automatically logs all incoming HTTP requests, recording the method, path, status code, and response duration.
  Technical Pointers: Add a correlation ID (X-Request-ID) to the initial request payload and pass it down through the controllers so you can trace a single user's action across all corresponding database logs.

[whitezaddy]

I have experience for this and have reviewed the code; I can submit a PR within 2 days.

[grantfox-oss]

🦊 GrantFox — @whitezaddy 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 #176)
2. Your PR will be reviewed by the BETAIL-BOYS maintainers

Good luck! Track your progress on GrantFox.

[lahdlahd]

I have experience for this, cause I've implemented structured logging in production Node.js APIs using both Pino and Winston, replacing raw console calls across large codebases. I can refactor the global logging architecture to output flat JSON with timestamps, log levels, and request IDs and implement Express middleware to automatically capture method, path, status code, and response duration on every request. I'll wire in X-Request-ID correlation IDs end-to-end through controllers and DB logs so individual user actions are fully traceable, also making the output ready for immediate ingestion by CloudWatch or ELK. Clean, zero-regression refactor delivered within the estimated timeframe