Diagnosing .NET 6 issues from sidecar containers using dotnet-monitor

Mike Rousos continues his series on how to use .NET CLI tools to diagnose common performance and reliability issues by showing how dotnet-monitor can be used to easily diagnose issues in Kubernetes clusters from sidecar containers.
Links:
dotnet-monitor GitHub repo: github.com/dot...
dotnet-monitor Docker image: hub.docker.com...
The small sample app I diagnosed: github.com/mjr...
Documentation on other .NET CLI diagnostic tools: docs.microsoft...
Previous similar On.NET shows I’ve recorded that folks may want to refer back to:
Diagnosing thread pool starvation with dotnet-counters and dotnet-dump: docs.microsoft...
Diagnosing managed memory leaks with dotnet-dump: docs.microsoft...
Diagnosing high CPU usage with dotnet-trace: docs.microsoft...
Diagnosing LOH issues w/ GC traces from dotnet-trace: docs.microsoft...
🙋‍♀️🙋‍♂️ Get your questions answered on the Microsoft Q&A for .NET: aka.ms/dotnet-qa
🏫 Learn C#, F#, and .NET with free self-guided learning from Microsoft Learn: aka.ms/learndo...
#dotnetmonitor #dotnet #performance

[@KarthikMcyclist]

James is awesome ! As always great session..

[@w32crazydev]

Would be great if we could use this with docker too and share that ipc via unix sock. Still cant do this in docker desktop on windows it seems

[@arunsinghk1]

This is great. Thank you.

[@obiwan_smirnobi]

Thanks for the video! 🔥

[@kylenic33]

Seems like I'm already covered via metrics I export from dotnet with prometheus and grafana dashboards. Ideally it would be nice to debug via IDE (Rider/VS) a running build in staging env.

[@OeHomestead]

Very useful indeed :)

[@vivekanandkoppula5464]

How is it different from dapr side car container.

[@mikerousos4036]

The side car technology used is just a detail. What I wanted to highlight here was how dotnet-monitor can be used from a side car to easily gather diagnostics. I haven't tried using dotnet-monitor in a dapr side car, but my guess is that it would work there the same as any other scenario. I'll try that out soon to see how it goes!

[@S3Kglitches]

hi what about so many VS 2022 Razor tooling issues? Most importantly, the editor.