-
-
Notifications
You must be signed in to change notification settings - Fork 213
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
.NET Profiling for ASP.NET Core #2316
Labels
Comments
Very exciting. How long do you think it'll be before external users are able to give it a go, assuming that we acknowledge that it's "alpha/beta caveat emptor" :) |
First we need to get through #2315, which is blocked by microsoft/perfview#1829 Then we can better estimate this one. It will likely be a while. |
This was referenced Feb 2, 2024
This was referenced Feb 10, 2024
This was referenced Feb 20, 2024
This was referenced Mar 12, 2024
This was referenced Apr 11, 2024
This was referenced Jun 27, 2024
This was referenced Aug 15, 2024
This was referenced Nov 3, 2024
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Follow up from:
collect
Microsoft-Windows-DotNETRuntime
rundown provider (loaded libs, etc) in a separate session and merge with actual samples later during processing, if possible (merging nettrace files, or having a custom provider for TraceLog).Or maybe we don't even need to collect these because we're in the same process? can we hack our way around and get the libraries from the current process instead? Probably not so easy because it also somehow stack walking if I'm not mistaken.
We'll use GlobalMode to set the behavior: all threads in process (global Mode) or only activity/request (server mode)
Consider capturing only the current "activity", i.e. not all threads but only what belongs to the transaction.
See also https://studylib.net/doc/6851938/eventsource-activity-support
possible blocker Missing activity in case of "broken" ActivityID in events microsoft/perfview#2122
The text was updated successfully, but these errors were encountered: