While monitoring server health using .NET Agent is it possible to co relate Perfmon-> ‘memory:% committed bytes in use’ or ‘memory: available MBytes’ with the operation of the application is affecting it? Like if available memory goes down how can I know which operation is causing this? We are only focusing on the w3wp process data here as the .NET application is deployed in IIS.
Should I look for the highest no of stalls in an agent (under a particular host name) to assume the reason for memory crunch? Is it the right approach ? I am not sure whether this is the right APM diagnostic approach. Kindly advice.
Just for completeness, you should not rely on default Windows counters for CPU and Memory if you're running on VMware.
You should instead use the counters available from VMware Guest Tools.
Those metrics are directly related to what's available for counters in PerfMon.
Windows does not have a counter that allows the use of "% committed bytes in use" per process.
There are other memory counters under "Process" that you can monitor.