Logging isn’t blocking, can you share a snipit of tracing config

https://gist.github.com/manuel-delverme/1f0160a51d67d1fddd47cb10b574a963 Test 1-b Duration: 1.7479286193847656 Test 1-a Duration: 2.0280649662017822 Test 2-b Duration: 1.0003631114959717 Test 2-a Duration: 1.0003926753997803 Test 3-b Duration: 11.34163522720337 Test 3-a Duration: 21.62044596672058 To exit a span it has to block execution, I would have expected a result like: Test 1-b Duration: 1.7479286193847656 Test 1-a Duration: 2.0280649662017822 Test 2-b Duration: 1.0003631114959717 Test 2-a Duration: 1.0003926753997803 Test 1-b Duration: 1.7479286193847656 # No delay, the uploading is async Test 3-a Duration: 11.62044596672058 # Rightfully delayed as data needs to mo

Manuel D. noted your point here. Discussing with team will circle back.

Manuel D. I think this is an issue with our new register_otel function. Appologize. We created the above simple function to remove a bit of boilerplate in setting up OTEL span processor. In that code, we did not add an option for the BatchSpanProcessor only the SimpleSpanProcessor The BatchSpanProcessor is non-blocking while the SimpleSpanProcessor is blocking We will fix. For now, you can use the manual configuration version at the bottom of this page to setup the BatchSpanProcessor. https://docs.arize.com/arize/large-language-models/tracing/manual-instrumentation/python

--------- Manuel D. If you want to take a look at the SpanProcessors they are here. Pretty well tested OTEL code. https://opentelemetry-python.readthedocs.io/en/latest/_modules/opentelemetry/sdk/trace/export.html#SpanExportResult

Thank you Jason!