tailg8nj commented on PR #70758: URL: https://github.com/apache/airflow/pull/70758#issuecomment-5876341113
> I looked at the linked issue. Can you explain the motivation behind using an external tracer_provider? Maybe an example use-case? I believe this to be fairly well documented in the linked issue. Open telemetry offers a way for vendors to ship distributions that preconfigure their preferred settings of the SDK and other auto-instrumentation features. These are not limited to: collector endpoint, format and compression, additional span processors, propagation strategies (like setting trace state), framework and library instrumentation preferences (like urllib, requests, httpx, celery, etc). It is a well supported valid way of setting up your Python asset w/o code. Whether or not internal spans eventually get added can be address by the vendors themselves. How else do you suggest we address issues 1 and 2 from the linked issue? -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
