Hi Ceph community, We enabled the native Jaeger tracing on the OSDs of our Ceph 19.2.3 cluster to get distributed tracing. Issues: 1. Every OSD continuously logs this following error, [Error] File: /home/jenkins-build/build/workspace/ceph-build/ARCH/x86_64/AVAILABLE_ARCH/x86_64/AVAILABLE_DIST/centos9/DIST/centos9/MACHINE_SIZE/gigantic/release/19.2.3/rpm/el9/BUILD/ceph-19.2.3/src/jaegertracing/opentelemetry-cpp/exporters/jaeger/src/recordable.cc:95[TRACE JAEGER Exporter] SetAttribute() failed, attribute type not supported 2. In Jaeger we only see two standalone spans per op (op requested/created and enqueue). They are not connected to each other or to any client-side trace. Questions 1. Is the SetAttribute() error a known issue, and is there a fix or workaround? 2. What is the intended use of these two spans? Is there a way to get full end-to-end traces in current releases? If anyone has faced this or knows a fix, please let us know. Thanks & Regards, Kathirvel T Associate R&D Engineer 9025610912 mailto:manoj.kumar@zybisys.com kathirvel.t@zybisys.com https://www.zybisys.com https://in.linkedin.com/company/zybisys https://www.facebook.com/Zybisys/ https://www.instagram.com/ZyBiSys/ https://www.youtube.com/@zybisys https://www.facebook.com/Zybisys/ Disclaimer : The content of this email and any files transmitted with it are confidential and intended solely for the use of the individual or entity to which they are addressed. If you have received this email in error, please notify the sender and remove the messages from your system. If you are not the named addressee, it is strictly forbidden for you to share, circulate, distribute or copy any part of this e-mail to any third party without the written consent of the sender. E-mail transmission cannot be guaranteed to be secured or error free as information could be intercepted, corrupted, lost, destroyed, arrive late, incomplete, or may contain viruses. Therefore, we do not accept liability for any errors or omissions in the contents of this message, which arise as a result of e-mail transmission. The recipient should check this e-mail and any attachments for the presence of viruses. The company accepts no liability for any damage caused by any virus transmitted by this email."