Community
- Command Central
- MVP Program
- Monthly Mission
- Blogs
- Groups
- Events
- Media Vault
Products
- Observability
- Network Management
- Application Management
- IT Security
- IT Service Management
- System Management
- Database Management
Content Exchange
- SolarWinds Platform
- Server & Application Monitor
- Database Performance Analyzer
- Server Configuration Monitor
- Network Performance Monitor
- Network Configuration Manager
- SQL Sentry
- Web Help Desk
Free Tools & Trials

Orion APM incorrectly reports high CPU on WMI process monitor

I utilize WMI relatively heavily to monitor different processes on our Windows Systems. There have been several cases now where the process will get flagged in a Warning state for utilizing a lot of CPU; however, when I log into the system it shows that the CPU utilization for that process is zero.

In my case that just happened I did confirm that the process ID was correct and I also used the WMI browser in the Engineers Toolset and it reported the CPU correctly at zero utilization for that process.

Is this a known issue?

Any suggestions here would be greatly appreciated, thanks!

Find more posts tagged with

Accepted answers

All comments

jiri.tomek

Hello Byron,
is it possible that mentioned process really had CPU spike during measurement? APM gets two measurements with 5 seconds delay between and compares them to get actual CPU usage. How often does this happen? Would it be possible to setup performance counter for specific process CPU to have some independent data available?

We would need detailed logs for further investigation so if you are sure that APM reports CPU incorrectly, please open a support case.

byrona

Well, I watched it over the course of at least 30 minutes on both APM and with Windows Task Manager and according to Task Manager it was always very low and according to APM it was at the same High CPU the entire time. I confirmed that APM was looking at the correct PID. I did grab screenshots of it all and restarting the service on the Windows System did resolve the issue.

I will probably have to wait and open a support ticket when I catch it again. I don't see it happen very often, only a few times so far and it's not something that I can reproduce on my own.

byrona

This is happening again so I just opened support case #197968.

MarieB

Great Byron--will you post back when you get the results?

Thx,

byrona

I will post my results; however, I lied to you all. This is actually a SNMP process monitor, not WMI. I apologize for my confusion. I am used to using WMI for all of our Windows stuff and this was the one exception.

I am still working with Support and will post my results as soon as I have them.