Enhancement/Customize AppInsights Endpoint #306
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
c-w
force-pushed
the
enhancement/customize-appinsights-endpoint
branch
from
99edb01
to
27d2324
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Some users of Azure Application Insights may have a requirement to customize the AppInsights telemetry endpoint, e.g. to make the service work in Azure Government or Azure China or to leverage a local deployment of AppInsights.
As such, this pull request adds an environment variable that can be used to customize the AppInsights telemetry endpoint. If the variable is not set, the default PaaS/hosted-service endpoint of AppInsights is used as was the case prior to this pull request.