Invalid CPU Statistics (Flaw)

I just noticed an incorrect graph on 1 of my servers, I usually look at the graphed line and not the Percentages. I exported the data and found that the server shows -150 for a value for MIN CPU LOAD.

Why would ORION accept a negative value for CPU Load? I would think that any number being reported by a system would have to pass a validation test, but that is just my opinion.

Here is what I am seeing: (I really like how the graph gets skewed to 2000%

Find more posts tagged with

chart

cpu_graph

cpu_utilization

Accepted answers

All comments

Bohumil_Klimek

Thank you for your post, I am unable to reproduce it. Is it happening only with device on the screenshot (USKSOLA1FT01) or all of them? If only for this device what type of device is it? Manufacturer and model would be great to know.
Bohumil Klimek • SolarWinds • QA Tester

justty

I found this on 1 server so far. I sent Brandon Shopp an email, as we have an open case with him regarding the "flaws" we have identified in ORION. We believe that this SQL table/ORION should never accept a negative number for CPU. What good is ORION if it is showing "bad" data.

We believe the data should go through an integrity check before ORION accepts it.

Anyways, how would you "reproduce" a negative number from the CPU? Are you just trying to update the SQL Table?

ecklerwr1

Odds are Orion is just showing the number it's getting from the snmp agent on the device.... so it's debatable whether this is really a flaw.

PetrKnyttl

justty - t - I see at the moment 2 possible reasons:

1) SNMP response - just what ecklerwr1 said already

2) Chris LaPoint in the earlier post replied to the same question:Typically, we see this when the monitor is just starting up because it requires two polls to calculate CPU utilization. We have seen this happen due to mathematical anomolies when the counter rolls over.

Regarding the validation of the data, it's already noted and will be discussed