Under Enable W3C Distributed Tracing Support For Classic ASPNET Apps it stats that
> Starting with Microsoft.ApplicationInsights.Web and Microsoft.ApplicationInsights.DependencyCollector, no configuration is needed.
We're not seeing this active, but we've been using AppInsights for a long time and have updated through previous versions to get to where we are now. Does the statement above mean that "When you install those packages, the configuration is put in place for you" or "When you install those packages, the configuration is no longer required"? Obviously number 1 means that we'll need to update the config ourselves when we update versions, but version 2 means that if we left our config "as-is" it would be enabled
⚠Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.
@MatthewSteeples Thanks for the question! We're investigating this and will get back to you shortly.
@mrbullwinkle I believe the note intends to indicate this rather:
Starting with
Microsoft.ApplicationInsights.WebandMicrosoft.ApplicationInsights.DependencyCollectorversion 2.8.0-beta1, no configuration is needed.
Is that the intent indeed?
I don't believe that is correct in 2.8.0-beta1 the functionality was available but it was disabled by default and you had to manually configure the ApplicationInsights.config file with the following:
- Under RequestTrackingTelemetryModule -
Add the EnableW3CHeadersExtraction element with value set to true.
- Under DependencyTrackingTelemetryModule -
Add the EnableW3CHeadersInjection element with value set to true.
Add W3COperationCorrelationTelemetryInitializer under the TelemetryInitializers
similar to:
<TelemetryInitializers>
<Add Type="Microsoft.ApplicationInsights.Extensibility.W3C.W3COperationCorrelationTelemetryInitializer, Microsoft.ApplicationInsights"/>
...
</TelemetryInitializers>
With the latest stable releases of Microsoft.ApplicationInsights.Web and Microsoft.ApplicationInsights.DependencyCollector this is no longer the case this should all be enabled by default simply by adding those packages and those configuration options are now obsolete.
So I believe what we are saying in that section is you should be able to upgrade the underlying packages to the latest stable release and this functionality will be enabled for you automatically without any other changes required.
adding @cijothomas to confirm if I am missing anything.
Correct.
"no configuration is needed." here means "no special additional config is required".
@mrbullwinkle This page requires a full rewrite. Can you schedule an item for this. We can discuss structure and specifics in our weekly sync.
@cijothomas I will create a separate internal workitem to track so this issue and can be closed out by CXP and will touch base with you next week. Right now we are booked out getting content for Build ready. Thanks!
@mrbullwinkle @cijothomas Thanks for clarifying!
@MatthewSteeples Thank you very much for bringing this to our attention! We're tracking this issue internally and will now proceed to close this thread, but if there are any further questions regarding the documentation, please tag me in your reply and we will be happy to continue the conversation.