I'm trying to investigate some slowdowns within some .Net Core code and the purepath is not very helpful I just seem to have the IIS web request -> Sync invocation -> AspNetCore WebRequest -> Async invocation -> SyncWork -> Async Invocation.
Is there some setup I haven't done to get further insights into the .net core code itself (method names etc) or do I have to instrument them myself?
Believe we are running latest one agent 1.175.270
.Net Core 2.2.6 running under IIS
Answer by Sebastian K. ·
The issue is that, there are executions of your internal code methods. In such case you may not see them on purepath without putting extra sensors using Request Attributes. To investigate it, pick some sort of purepaths that mathes the same patterns (ex. url + response time X s +) ans then drill down into method hotpots. You will see what part of your code keeps more time on CPU and what less.
If you will find method that may bee root cause create Request attribute based on .NET Method:
Restart your process and you will see it on purepath. You can make on top of it custom service as well if this will be better for you.
How nginx and IIS .NET instrumented 1 Answer
Long time in AcquireRequestState 1 Answer