win2003 OID , process CPU and MEM monitoring

jabbasi · Post by **jabbasi** » Sun May 21, 2006 1:45 pm

Hi
I have done lots of searches, to find OIDs for win2003. without any luck, if any one knows where or how I can get those, that will be much appreciated.

I am also trying to monitor Process CPU % and Mem usage for that process.
Does anyone know how to do this in Cacti? or if anyone has templates for this kind of monitoring?

I am not intrested in How much Total CPU or Mem usage is on the box, but I am intrested in monitoring a Process to see how much CPU and Mem a process is using.

Any hints or help will much appreciated.

thanks

BSOD2600 · Post by **BSOD2600** » Sun May 21, 2006 2:07 pm

Check out the 'running processes' link in my signature.

jabbasi · Post by **jabbasi** » Mon May 22, 2006 8:46 am

thanks much appreciated.
I will take a look at it

jabbasi · Post by **jabbasi** » Sun May 28, 2006 8:25 pm

I tried this, and it works well.
I have a question though regarding this, that what happens if processes are stopped for a while, and restarted again, are they monitored automatically or you have to repply the templae , or run query to get list of running processes and reselect all those processes you want to monitor.
or what if I decide to not monitor a single process, and stop graphing for that?

thanks

BSOD2600 · Post by **BSOD2600** » Mon May 29, 2006 11:41 am

Cacti will reindex if the number of open processes changes, so then it will find the new process.

jabbasi · Post by **jabbasi** » Sat Jun 10, 2006 11:54 am

I am not sure if I understand what you mean.

But here is what I see

process A was runing, (running process) query was applied, cacti starts monitoring this Process A, all works well.

ProcessA is stopped for a few hours, and resarted again, but cacti never starts monitoring this process, until after this ( running processes) query is removed from this machine and re-applied to it.
atleast thats what I see.

thanks

BSOD2600 · Post by **BSOD2600** » Sat Jun 10, 2006 1:03 pm

When process A is running, lets say there are a total of 43 processes. Once process A stops, the process count goes to 42 and triggers cacti to reindex.

The problem arrises is when between polling cycles. A new process is started, one ends and thus the total count never changes, so cacti doesn't re-index and find the new process.

jabbasi · Post by **jabbasi** » Sat Jun 10, 2006 5:45 pm

thanks a lot