You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
As discussed at various times, here is some telemetry to _maybe_ help us
track down tag helper issues.
I'm no telemetry expert here, but my hope is with these queries we'll be
able to find things like:
* Occurances of tag helper discovery never finishing (i've seen this on
my machine, but maybe nowhere else?)
* Where tag helper discovery results in us losing tag helper information
* Sessions that never get a non-zero number of tag helpers
* How often we're trying to discover tag helpers in general
(with/without any changes)
Please keep that in mind when reviewing. I don't know how to write the
Kusto queries for those, I'm just assuming that I, or someone smarter
than I, will be able to work it out later :)
Also removing some old telemetry which I don't think we've ever used,
and looking at the data, I'm not sure what problem we thought we had
that we were looking for, but we don't seem to have it. Either the
response is instant, or the data is bad. Neither is useful.
<img width="127" alt="image"
src="https://github.com/dotnet/razor/assets/754264/c99d78e1-b2ca-4474-a33e-9807288e9910">
// Only allow a single TagHelper resolver request to process at a time in order to reduce Visual Studio memory pressure. Typically a TagHelper resolution result can be upwards of 10mb+.
0 commit comments