.Net Core DebugDiag Equivalent

Viewed 1082

For .Net 4.6.x, I have heavily relied upon DebugDiag 2

Anytime Production applications had high CPU issues, deadlocks, etc, I would use that tool to capture dumps of w3svc and it prints out a nice report of what all the threads were doing. They may be waiting on 3rd party APIs, databases, etc.

I want to move to asp.net core, but if I had a production server w/ 100% CPU or issues like mentioned above, I can't find any way you can dump all the threads in a process and see their stack trace.

How are people getting around not having this visibility available to them? Am I missing something? I'm looking for a solution that works in Linux as well.

1 Answers

I would recommend IDA which is a debugger and disassembler. It runs on Linux and can be used to dump all the threads and perform stack trace. Here is a link to it. Or Microsoft now allows you to debug directly from Visual Code Studio and dump threads onto there. There are multiple tutorials on that and a quick Google Search can help or viewing the Microsoft help center. Check that out here.

Related