Improve Logging Practices in the Repository

[snobbee]

Is your feature request related to a problem? Please describe.

Currently, the repository lacks a robust logging system, which can hinder our ability to debug issues and monitor application performance effectively. Without structured logging and proper correlation IDs, tracing requests across different components will be challenging.

Describe the solution you'd like

I propose implementing a comprehensive logging strategy that includes:

• Adoption of structured logging using JSON format for all logs.
• Inclusion of standard fields such as timestamp, severity level, and correlation IDs.
• Support for different log levels (DEBUG, INFO, WARN, ERROR) to categorize log messages appropriately.
• Context injection to provide meaningful information with each log entry.
• Implementation of log retention policies to manage log storage efficiently.

Describe alternatives you've considered

• Relying on plain text logs, which could lead to inconsistent formats and make it difficult to parse logs for analysis.
• Using third-party logging services without integrating structured logging practices.

Additional context

Implementing these changes will enhance our debugging capabilities, improve the monitoring of application performance, and ensure that we have a consistent logging pattern across the codebase. This will ultimately lead to better observability and faster issue resolution.