Add env var to control sending telemetry to appinsights in functions worker #1621
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Follow up to #1509
We have decided to separate out the context propagation and enabling azure monitor functionality. To do this, we will be using a separate env var
PYTHON_APPLICATIONINSIGHTS_ENABLE_TELEMETRY
, which will be for strictly sending telemetry to appinsights and as well enabling context propagation. Future configuration of the telemetry SDK will most likely have the word_APPLICATIONINSIGHTS_
inside it's name.We treating Opentelemetry context propagation as a separate feature. This will be controlled as an opt-in like before with
PYTHON_ENABLE_OPENTELEMETRY
env var.