Maximum Values

I have to solve the same problem! Creating a formular sensor with min/max doesn't work:

#1:Licence-max Max(Channel(2082.0))

...delivers also the maximum average value of the view, not the absolute maximum value in the period.

regards, Ralf

Hello,

I'm afraid the issue simply stems from the fact that the monthly and yearly graphs (in fact all graphs except the 'Live Graphs') are sampled graphs (and tables). This can simply not be changed (nor would it be possible to graph all raw real-time collected values into one graph for one year), and so the maximum and minimum values are averaged as well. However, you could consider using the Historic Data Function to put out non-averaged values for one day, once you determined the day which had the maximum with the yearly/monthly graphs.

Best Regards.

I too am having real problems with this automatic averaging of all my data. I'm only interested in maximums and not averages for many of the metrics I'm monitoring which makes all of the historic data fairly useless afaik. Would I be correct in thinking that historic data is consolidated by re-writing averages to a new database table, discarding the original data? Would it not be possible to allow a change to this consolidation function to specify taking the maximum, minimum, average or percentile calculations instead for a given channel?

Hello,

minimum and maximum values would only make sensor for gauge-sensor types, and then it's simply technically not possible in the moment. And changing this, would require huge revisions on PRTGs code, so most likely this will not be changed in the near future.

Best Regards.

you keep answering this issue with a standard response... you can't do it technically. when will your code be able to 'technically' maintain the maximums and not the averages in the historic graphs.. almost ALL of our needs are to find out what the peaks were. we don't really give a rip what the averages are.. they are totally useless to us.

even for traffic monitors over time.. we don't need to see how it averages out (and down) over time looking at month, year, etc. We want to compare today's real values to historic values that also show the peaks.

Right, so we have to pull historic graphs to get the numbers we need.

Poll your customers and I think you would find that this is something useful, and the fact that the historic graphs erode and don't really reflect what has happened.

Please please please consider this alternatives for keeping history. carry forward the peak number rather than averaging a range. that can't be technically impossible to do.

thanks!

Ich kann die Durchschnittswerte bei den entsprechenden Sensoren auch kaum brauchen. Nett wäre es wenn ich das für alle betroffenen Sensoren oben im Kategoriebaum einstellen könnte. (Falls das nicht schon möglich ist). Weiters würde ich mir eine flexible Digrammanzeige wünschen: Ausschnitt vergrößern verkleinern. Verschieben mit der Maus. Vielleicht auch ein Radio Button ob Average oder Maximum angezeigt wird. Übersichtlicher wäre vielleicht auch eine farbliche Kennzeichnung der Tage oder Wochen. Auch eine direkte Anfang- Ende-Eingabe wäre praktisch (passt sich automatisch in das Fenster ein). und noch vieles mehr um uns die Arbeit zu erleichtern und sich von der Konkurenz abzuheben ;-)