Implement New Logging Mode: 'Threads' for Grouped Log Management

[Bardin08]

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

Yes. The problem arises following a sequence of related log events within a Telegram channel. All logs are posted as separate messages, making tracking and analyzing logs about the same operational issue challenging.

Describe the solution you'd like

I want to introduce a new logging mode called 'Threads'. This mode would automatically group related logs into threads within a Telegram channel, utilizing the comments feature to link logs with similar identifiers. This approach would significantly improve the readability and manageability of logs, especially in complex debugging or incident resolution scenarios. Features of this mode should include:

• Automatic detection and grouping of logs based on configurable criteria (e.g., traceID, spanID).
• Posting related logs as comments under a primary log message to maintain their contextual relationship.
• Customizable settings to define what constitutes a "related" log, allowing teams to adapt the feature to their specific logging needs.

Describe alternatives you've considered

The alternative relies on external tools for log analysis, which adds complexity and dependency on third-party services.

Additional context

Implementing 'Threads' would address the current gap in efficiently managing and analyzing related log events directly within Telegram channels. This feature is especially crucial for monitoring and troubleshooting complex systems, where understanding the sequence and relationship between log events can significantly impact incident response times and effectiveness.