ApplicationInsights-dotnet
ApplicationInsights-dotnet copied to clipboard
Do not track /Blazor as a single request.
Is your feature request related to a problem? The GET "/blazor" operation is skewing all time-based results because it looks like a single request (that can be very long).
Describe the solution you'd like. Track the request as individual operations so that the durations better represents what's actually happening
Describe alternatives you've considered. Ignore "/blazor" is the only thing I can think of, but I am unsure what else I'll miss.
Additional context. Blazor server .NET 6 Hybrid blazor and razor pages Installed SDK (in startup) App services on Linux Below you can see a 5-minute operation that actually had many super-fast operations.
This issue is stale because it has been open 300 days with no activity. Remove stale label or this will be closed in 7 days. Commenting will instruct the bot to automatically remove the label.
Based on my experience this still seems to be an issue.
Microsoft integration with Blazor is very poor. folks have been asking for this to be fixed but so far no action has been taken by microsoft.