Hello together

I'm trying to set up some Maps for our company. I used a few Gauges (the ones which look like a speedometer). My problem is now that they "autoscale" with the highest value they had. So the same value looks different on every device. I tried "Vertical Axis Scaling" on manual, but this only works for graphs. The Spikefilter would work, but if the value is higher than the limit I want to display, it's simply 0.

Maybe this is a bit confusing, so here an example:

I'm displaying the cpu ready value as an gauge for multiple devices. Now I want every Gauge having the same range (ex. 0 - 100%) and displaying values over 100% the same as 100%. The yellow section starts by 50% and the red one by 90%. Now if a sensor once had an value of 300% it scales the range to this and 3/4 of the gauge range is red.

Article Comments

Hi there,

Please open the channel settings of the CPU-Channels and enable the "Spike Filter"-Option. There you enter "0" as the minimum and "100" as the maximum. This should normalize the gauges again.
https://www.paessler.com/blog/how-to-filter-spikes-from-graphs-in-prtg

Best regards.


Oct, 2017 - Permalink

Hi,

Thanks, I already tried that, but I still want to keep the values above 100%, but not display them in the gauge. The Spike Filter would delete all values over 100% and display it as 0%, correct?


Oct, 2017 - Permalink

Hi there,

That is right, but 300% CPU usage isn't possible. This is falsely offered by the monitored target device. So, technically, it wouldn't be an advantage to monitor values above 100% as 100% is the technical maximum for a CPU. However some Windows Servers offer false Values under heavy load, which PRTG monitors then.

Best regards.


Oct, 2017 - Permalink

Yes, sure CPU can't, but I'm talking about "CPU Ready", this value can be more than 100%


Oct, 2017 - Permalink

Hi there,

Now I got it. :)
Unfortunately, you can't scale the Gauges via a dedicated option such as "Gauge Scale Max"/"Min". Due to the low request rate for such a feature it is currently not planned to be developed and implemented in PRTG.

Best regards.


Oct, 2017 - Permalink