Windows service monitor is used to monitor serveral home made services. Once the service is started the Windows Service Monitor records the physical and virtual memory usage but does not show the CPU load of the service.
What could be causing this?
best bet here is that the MIB is not reading correct.
use the MIB walk feature of the Toolset and see what the MIB/OID is that is needed and then you may need to add a custom poller since it is not reading correctly as is.
Thought of that one to. This would mean that the Windows Service Monitor shipped with Orion is no good?! So the best thing is to create one of our own? That should not be the case! Anyone have the same issue, or can someone confirm that their CPU load is visible?
if no one else has problems with the build in Windows Service Monitor, then i will raise a support ticket to find out what the problem might be.
We just started using it today but have noticed the same thing. The funny thing is we are trying to use the built in APM 2.0 monitor for the Orion server and none of the processes are showing any CPU time. If I check them through task manager, I see they are using quite a bit of processor.
I have the same problem... am monitoring over 100 windows services... and not one reports any CPU usage, despite them using lots of CPU.
Is this a bug?
