---

Subject:	RE: CPU REPORTING INCORRECT VALUE
Author:	Dennis Stackley
Posted:	2019-08-01 22:49

Hi Jagan,

We have experienced the same behavior whereby after stopping the collectors or all of Zenoss for that matter, leaving it down for 15 minutes or longer, then bringing it up, we see false/impossible values for CPU and Interface utilization (greater than 100%). In all cases of this, the data points are defined as DERIVE. In working with Zenoss Support, we believe there is a COUNTER value stored before the collectors/Zenoss comes down. After the collectors/Zenoss comes up, Zenoss starts collecting the COUNTER values again. The difference is calculated between the two values but there could be several values missing between the two COUNTER values. The resulting derived value ends up being a higher and inaccurate value.

Zenoss Support has opened a case to get this fixed. Until that happens, we disable triggers for High CPU and High Interface utilization after bringing Zenoss up and closely watch the Event console until there are no more being created. After that, we enable the triggers.

HTH
Dennis Stackley
Systems Integration, Senior Advisor
NTT DATA Services

------------------------------
Dennis Stackley
Systems Integration, Senior Advisor
NTT DATA Services
Divide CO
7202551377
------------------------------