stockservice-go: Improve logging with efficient and clean visibility

[ZiyadBouazara]

Refer to the following link for an example of setup :
https://github.com/LordMoMA/Hexagonal-Architecture/blob/main/internal/logger/log_setup.go

Description:

To ensure the StockService-Go service maintains high reliability, scalability, and ease of maintenance, it's crucial to enhance the current logging mechanism. This improvement aims to provide more efficient and cleaner visibility into the application's operations, facilitating easier debugging, monitoring, and performance tuning.

Current Logging Setup:

• Logger Library: Logrus is currently implemented for logging purposes.
• Logging Levels: Basic logging levels (e.g., Info, Warning, Error) are in use.
• Log Format: Logs are primarily unstructured, making it challenging to parse and analyze.
• Log Storage: Logs are written to standard output and local files without centralized management.

Objectives:

1. Structured Logging:

   • Leverage Logrus's capabilities to implement structured logging, ensuring logs are output in a consistent and machine-readable format (e.g., JSON).

2. Enhanced Log Levels and Granularity:

   • Define and implement more granular log levels to capture detailed information without overwhelming the log files.
   • Ensure appropriate use of log levels across different modules and functionalities.

3. Performance Optimization:

   • Optimize logging to minimize performance overhead, possibly by asynchronous logging or log batching.

4. Centralized Log Management:

   • Integrate with centralized logging solutions (e.g., ELK Stack, Splunk) to aggregate and manage logs effectively.

5. Contextual Information:

   • Include contextual data (e.g., request IDs, user IDs) in logs to facilitate easier tracing and debugging.

6. Error Handling and Reporting:

   • Improve error logging to capture stack traces and relevant error details.

7. Configuration Flexibility:

   • Enhance logging configuration to allow dynamic adjustment of log levels and outputs without requiring application restarts.

8. Compliance and Security:

   • Ensure that sensitive information is not logged and that logging practices comply with relevant security standards.

Tasks:

• - Audit existing logging statements across the codebase to identify areas for improvement.
• - Refactor logging statements to use structured logging with Logrus.
• - Configure Logrus to output logs in JSON format and integrate with a centralized logging system (optional).
• - Optimize logging performance by evaluating and applying Logrus performance best practices.
• - Update documentation to reflect the new logging standards and configurations.