For very large existing services, it would seem that interfaces would need to be refactored to include space for a trace_contect (method1, calls method2, calls method3, which enqueues task to ThreadPool...). That sound correct?

can you make rewrites like recording rules on Collector level?

This was very helpful, thank you very much!

I am struggling how we can propagate trace across grpc services. Can you please provide some direction?

I know it's kind of a side conversation in the grand scheme of the Q&A, but the general conversation around selling the idea of Otel to the business, as well as vendors was very interesting. Being able to evaluate business impact of developer productivity tools and use that to drive how you talk to business stakeholders about them is really important in large organizations and, in my experience, often an ignored topic among software developers.

Yes as someone who wants to contribute to otel this video helps me alot to understand how it works

Hi guys! Thank for the video, it was really useful. By the way, can you share some materials on how to leverage context propagation to FastAPI auto-instrumentation?

Grande mestre Luiz! Sou fã.

Thank you, as always it was excellent

Can you to recommend best practices for using for OpenTelemetry to collect traces metrics .How to achieve auto-instrumentation.

Great insights

Very interesting episode,as always! Iris is very well spoken! Keep it up ❤