Enable full in-cluster support for OpenTelemetry within OpenShift Logging to unify observability capabilities, improve user experience, and streamline the monitoring and troubleshooting process for users deploying applications on OpenShift.

Reasons

1. Unified Observability: OpenTelemetry offers a standardized framework for collecting and correlating traces, logs, and metrics, helping to establish a holistic observability strategy across OpenShift environments. Our goal is to open a path for customers using current logging solution to features that Opentelemetry provides. 

1. Enhanced Troubleshooting and Diagnostics: By enabling detailed tracing and data correlation, users can efficiently diagnose performance issues and reduce mean time to recovery (MTTR). For customers using CLO troubleshooting integration with current logging stack is crucial. 

1. Developer and User Experience: For APM, our goal is to providie out-of-the-box support for telemetry data collection with minimal configuration. We want customers using CLO to be able to leverage the APM features.

1. Alignment with Industry Standards: OpenTelemetry is rapidly becoming the industry standard for observability. Supporting it natively in OpenShift Logging aligns the platform with current trends and customer expectations.

1. Future-Proofing: This decision positions OpenShift to adopt future enhancements and industry evolutions in observability practices, ensuring long-term relevance. We are especially aiming at customer using current logging stack who want to leverage Opentelemetry features. 

Implications

• Development Effort: Enabling OpenTelemetry support will require development resources to integrate with the existing OpenShift Logging framework and ensure seamless functionality.

• Performance Considerations: Accommodating additional telemetry data might impact system performance; therefore, performance testing and optimization will be necessary 

• Documentation and Training: documentation and user guidance will be required to assist users in adopting and leveraging the new features effectively.

• Backward Compatibility: Ensuring that the new features do not disrupt existing users who rely on current observability solution - CLO - is will be critical.