Implement Correlation IDs for Enhanced Logging and Tracing

[monilpat]

Feature Request

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

The current logging system lacks correlation IDs, making it challenging to trace requests across distributed services and identify the root cause of issues.

Describe the solution you'd like

Introduce correlation IDs in the logging framework to enhance observability and traceability. This should include:

• Generating a unique correlation ID for each request and propagating it across all services involved in handling the request.
• Including the correlation ID in all log entries related to the request to provide a comprehensive trace.
• Providing utilities to extract and log correlation IDs in existing logging statements.

Code Example

// Example of adding correlation ID to a log entry
logger.info('Processing request', { correlationId: req.correlationId });

Describe alternatives you've considered

• Using custom headers or metadata to track requests manually, which is error-prone and inconsistent.
• Relying solely on existing log messages, which do not provide the needed traceability.

Additional context

Implementing correlation IDs will significantly improve the ability to trace and debug complex interactions in distributed environments, enhancing both monitoring and troubleshooting capabilities.

Related Issues

• Issue #145
• Issue #144