9 May 2011

SCOM 2007 R2 - Pool NonPaged Bytes monitoring


One of the way to monitor Memory Leaks in the system is to monitor the NonPaged Pool Bytes performance counter.


 

Although any leak is serious, memory leaks are of particular concern when they involve the nonpaged pool. Many system services allocate memory from the nonpaged pool because they need to reference it when processing an interrupt and cannot take a page fault at that time. To identify whether or not a leak affects the nonpaged pool, include the following counters in your monitoring:

  • Memory \ Pool Nonpaged Bytes
  • Memory \ Pool Nonpaged Allocs
  • Process( process_name)\ Pool Nonpaged Bytes

This counter is not being monitored by default in SCOM. There're only performance collection rules for that(disabled by default) and self-tuned monitor for Exchange 2003 role servers(Exchange management pack).

But for some reason you maybe interested to monitor such counter with predefined threshold. In my case, it was needed to created a monitor disabled by default with threshold of 178257920 bytes.

You can access/download this management pack in XML format here.

 

p.s.

Excellent article about Paged and NonPaged Pool:  

http://blogs.technet.com/b/markrussinovich/archive/2009/03/26/3211216.aspx


No comments:

Post a Comment