Leighton Chen
Leighton Chen
@ashleysommer We will be rolling out images in which the `azure.monitor.opentelemetry` module will be pre-installed on the image itself so it will always exist (regardless if (1) is set). Thus,...
As a followup to the above, we introduced this pr: https://github.com/Azure/azure-functions-python-worker/pull/1621 We have decided to use separate app settings to control context propagation and enabling appinsights explitcily, the latter automatically...
Might not be applicable due to: https://github.com/open-telemetry/opentelemetry-python/issues/4561
@qiuge615 Please allow for maintainer edits so we can rebase for you.
This PR is quite big a complex. I suggest implementing this feature in different parts to ensure easier manual testing of each part.
@DylanRussell Does this apply to the other batch span/metric processors too?
@avramdj Thanks for the contribution! Please add a [CHANGELOG](https://github.com/Azure/azure-sdk-for-python/blob/main/sdk/monitor/azure-monitor-opentelemetry-exporter/CHANGELOG.md) entry and add a test for this to show that a custom `TracerProvider` can be used.
@lmolkova I'm assuming you are asking for functionality to ALLOW overriding of the global trace provider (like an option), not change the way the api works right?
I'm not sure if I agree with @xrmx 's [comment](https://github.com/open-telemetry/opentelemetry-python/pull/3992#pullrequestreview-2135099973) regarding making the resource detector loaded by default. We have [OtelResourceDetector](https://github.com/open-telemetry/opentelemetry-python/blob/main/opentelemetry-sdk/src/opentelemetry/sdk/resources/__init__.py#L305) loaded by default and it populates `service.name` by default...