Setup Structured JSON Logging

[nursetechie]

Issue #39 — chore: Setup Structured JSON Logging

Description

Standard console output is unparseable for production logging systems like Datadog or ELK. Implementing structured JSON logging ensures that logs are highly indexable, searchable, and machine-readable in production environments.

---

Requirements & Context

Architectural Goal: Improve operational observability.

Implementation Expectations: Integrate pino or winston. Replace all existing console.log and console.error calls. Configure the logger to output JSON in production, while utilizing pretty-printing for local development readability.

---

Acceptance Criteria

• Production logs output strictly as JSON.
• Errors include stack traces within the JSON structure.

---

Out of Scope

• Setting up log shipping agents (e.g., Filebeat).

---

Suggested Execution

git checkout -b chore/structured-logging

---

Suggested Commit Message

chore: implement structured json logging across application

---

Testing Notes

• Set NODE_ENV=production and ensure the terminal output is formatted as pure JSON.

---

References

Pino logger documentation.

---

Definition of Done

• Ready for review.

[OpensrcLord]

Hello @maintainer, 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. And I will deliver at the shortest possible time.

[Babigdk]

Hello @nursetechie, I'd like to work on this issue.

I have experience improving observability in Node.js/TypeScript backends using structured logging with Pino and Winston. I'm confident I can implement a clean, production-ready logging solution that aligns with the project's requirements while keeping the developer experience smooth.

My implementation plan includes:

• Integrating a high-performance structured logger (preferably Pino unless the project already favors another logging library).
• Replacing all existing console.log, console.error, console.warn, and related statements with a centralized logger utility for consistency across the application.
• Configuring environment-aware logging so production outputs structured JSON suitable for log aggregation platforms, while development uses a readable, colorized format.
• Including useful contextual metadata such as timestamps, log levels, request IDs (where applicable), and error stack traces to improve debugging and observability.
• Ensuring sensitive information is not logged by default and following logging best practices.
• Updating or adding documentation for the new logging setup and verifying that all existing tests and CI checks continue to pass.

I'll submit a clean, well-tested PR that fully satisfies the acceptance criteria and follows the project's coding standards.

Thank you for your consideration!