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

Why does Orion's CPU stats not match the CPU reported by the node?

Lately, we've had a node where Orion monitors the CPU via WMI and thinks it's constantly above 90%, for hours at a time. When I log into the node to view its resources (checked with perfmon and the task manager) it is not even close to that, about 30-50%, with basically no spikes above 70%. This is really concerning, we want to know if Orion is polling reliable information.

Has anyone experience something similar? Any ideas why?

Find more posts tagged with

WMI

Accepted answers

All comments

taylor.crowley

Might be worth giving the WMI service on the endpoint device a restart or maybe restart the whole machine if possible? Have you considered using an agent instead of WMI to see if you get the same results?

vinay.by

Raise a case with SolarWinds support, be it WMI or Agent or SNMP we do such odd scenarios. I have spent most of my time on SNMP polling and such scenarios can be fixed easily its just that i need to ask SolarWinds to poll the right OID's which i still can play around with. But since you are using WMI it depends on what classes it uses on the backend and maybe as taylor has mentioned below that could be a workaround and that might fix the issue for now. But then if you want to deep dive its best to raise a case.