.NET Framework & Process thresholds

Apr 16, 2009 at 1:00 PM
Edited Apr 16, 2009 at 1:08 PM
Hi Clint,

It would be very useful if PAL could support/could help with finding issues with .NET applications.
Issues related to Memory, Threading, Garbage Collector and stuff like that.
(Counters like .NET CLR Exceptions, .NET CLR LocksAndThreads, .NET CLR Memory, .NET CLR Networking etc.)

Is there any possibility / are there any plans to support this functionality in the near timeframe?


Apr 23, 2009 at 6:05 PM
I love your tool. I would concur with bsharp. If you have templates for .NET counters, please share with us. When is 2.0 going to be available?

Apr 28, 2009 at 12:20 AM
I agree. I've been meaning to create a more extensive .NET CLR threshold file, but my free time is limited and my focus is on development PAL v2.0 right now. I'm projecting to have PAL v2.0 available in beta form within the next 3 months. I'm more than half way finished. :-)

If you create one, then consider following the .NET performance thresholds established by the Microsoft Patterns & Practices Team. These are published on http://msdn.microsoft.com.