Sometimes PRTG WMI CPU Sensor will report values as high as 9,600%, invalidating all the historic graph data due to the incorrect graph scaling. I have seen this in more than one WMI CPU Sensor and will need a workaround to edit this values in order to correct these otherwise unvaluable CPU usage graphs.
Regards, Federico
Article Comments
Attention: This article is a record of a conversation with the Paessler support team. The information in this conversation is not updated to preserve the historical record. As a result, some of the information or recommendations in this conversation might be out of date.
Thank you very much! That seems to do the trick for live and 2 days graphs - I suppose the spikes on 30 days and 365 days graphs will be removed once they are updated.
Regards, Federico
Apr, 2015 - Permalink
I have tried to enable the spike filter on the Total channel (min 0% - max 100%) but 30-days & 365-days graphs still have spikes above 100%. Should I wait for PRTG to update graphs or restart it?
Apr, 2015 - Permalink
Recalculation is done in the background and can take some time, so I would wait until the graphs are updated.
Apr, 2015 - Permalink
Have you tried enabling the Spike Filter in the sensors channel settings?
Apr, 2015 - Permalink