Add OTel compatible telemetry

[daniel-orlov]

Is your feature request related to a problem? Please describe.
Currently, our server lacks comprehensive telemetry capabilities, which makes it challenging to gather essential performance and operational data. Proper telemetry is crucial for monitoring, debugging, and optimizing the server's performance and resource utilization. Adopting an open telemetry standard will provide a unified and interoperable approach to collecting and exporting telemetry data.

Describe the solution you'd like
I propose adding open telemetry compatible telemetry to our server. OpenTelemetry is an open-source project that provides a vendor-agnostic and standardized way to instrument applications for telemetry data collection. By integrating OpenTelemetry into our server, we can gain insights into various aspects of the application's performance, including:

1. Distributed Tracing: Implement distributed tracing to monitor the flow of requests across multiple services, identifying bottlenecks and performance issues.
2. Metrics Collection: Gather essential performance metrics, such as request latency, error rates, and resource usage, to analyze server health and efficiency.
3. Context Propagation: Ensure context propagation across different parts of the server and services, allowing us to correlate related telemetry data accurately.
4. Compatibility: Guarantee compatibility with popular telemetry backends, such as Jaeger, Prometheus, and Zipkin, by adopting the OpenTelemetry standard.

Describe alternatives you've considered
Without adopting OpenTelemetry, we might have to rely on custom telemetry solutions or third-party libraries that could lack standardization and interoperability. By embracing OpenTelemetry, we align with industry best practices and facilitate better integration with existing monitoring and observability tools.

Additional context
Incorporating open telemetry compatible telemetry will significantly improve our server's observability, making it easier to detect and diagnose issues. Any specific preferences or considerations for telemetry backends or data exporters should be discussed to ensure seamless integration.