-
Notifications
You must be signed in to change notification settings - Fork 123
Make W3C Correlation default and leverage native W3C support from new System.Diagnostics.DiagnosticSource Activity #958
Conversation
...plicationInsights.AspNetCore/DiagnosticListeners/Implementation/HostingDiagnosticListener.cs
Outdated
Show resolved
Hide resolved
...plicationInsights.AspNetCore/DiagnosticListeners/Implementation/HostingDiagnosticListener.cs
Show resolved
Hide resolved
...plicationInsights.AspNetCore/DiagnosticListeners/Implementation/HostingDiagnosticListener.cs
Show resolved
Hide resolved
...plicationInsights.AspNetCore/DiagnosticListeners/Implementation/HostingDiagnosticListener.cs
Outdated
Show resolved
Hide resolved
...plicationInsights.AspNetCore/DiagnosticListeners/Implementation/HostingDiagnosticListener.cs
Outdated
Show resolved
Hide resolved
...plicationInsights.AspNetCore/DiagnosticListeners/Implementation/HostingDiagnosticListener.cs
Outdated
Show resolved
Hide resolved
...plicationInsights.AspNetCore/DiagnosticListeners/Implementation/HostingDiagnosticListener.cs
Show resolved
Hide resolved
...plicationInsights.AspNetCore/DiagnosticListeners/Implementation/HostingDiagnosticListener.cs
Show resolved
Hide resolved
...plicationInsights.AspNetCore/DiagnosticListeners/Implementation/HostingDiagnosticListener.cs
Outdated
Show resolved
Hide resolved
...plicationInsights.AspNetCore/DiagnosticListeners/Implementation/HostingDiagnosticListener.cs
Outdated
Show resolved
Hide resolved
test/Microsoft.ApplicationInsights.AspNetCore.Tests/Helpers/CommonMocks.cs
Show resolved
Hide resolved
This reverts commit 2f1427a.
...icrosoft.ApplicationInsights.AspNetCore/Implementation/TelemetryConfigurationOptionsSetup.cs
Show resolved
Hide resolved
...plicationInsights.AspNetCore/DiagnosticListeners/Implementation/HostingDiagnosticListener.cs
Outdated
Show resolved
Hide resolved
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
left a couple of comments, the only major one is correlation-context on 2.x case with W3C headers.
…n 7.2 which is required for new Activity span types.
private static void ReadCorrelationContext(IHeaderDictionary requestHeaders, Activity activity) | ||
{ | ||
string[] baggage = requestHeaders.GetCommaSeparatedValues(RequestResponseHeaders.CorrelationContextHeader); | ||
if (baggage != StringValues.Empty && !activity.Baggage.Any()) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
if you want to avoid adding baggage to Activity that already had some baggage (why?) check for baggage presence before you read headers and return.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Got it.. will address it next PR (for 3.0 support)
20, | ||
Message = "Message: '{0}'.", | ||
Level = EventLevel.Verbose)] | ||
public void HostingListenerVerboe(string message, string appDomainName = "Incorrect") |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
public void HostingListenerVerboe(string message, string appDomainName = "Incorrect") | |
public void HostingListenerVerbose(string message, string appDomainName = "Incorrect") |
Also, do we really need both: Informational and verbose?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Will address it next PR (for 3.0 support)
AspNetCore RequestCollection specific changes, followup for the base SDK changes introduced in the PR:
microsoft/ApplicationInsights-dotnet#1193
Also Fixes:
#956
#900
To do:
3.XX support (separate PR)