[FEATURE] Equip ConversationManagers with telemetry #617
Description
Problem Statement
The built-in implementations of ConversationManager interface lack OpenTelemetry traces, making it difficult to monitor and debug conversation management operations in production environments. This limits observability into critical operations like context reduction, token limit handling, and general conversation management.
Proposed Solution
No response
Use Case
Developers will use OpenTelemetry traces to monitor conversation management performance in their production environments. Teams will be able to effectively debug issues related to context window overflows when they occur. Operations teams can track conversation state changes and recovery operations in real-time. Engineering teams will gain insights into the frequency and impact of token limit issues across their deployments. Product teams can measure and compare the effectiveness of different conversation management strategies through trace data.
Alternatives Solutions
No response
Additional Context
No response