Even if the code were changed to add a new 'per5min' option, then you'd still have the problems caused by Data Normalisation resulting in decimal values instead of whole numbers.
You can set the 'integer' option, and the 'fixunit' extended option, to display in the closest integer and prevent 0.5 being displayed as 500 mpages. This can help, but unless you adjust the data collection to be exactly on the 5min boundary you'll be getting the effect of data normalisation. Tobi is rather reluctant to add an option to MRTG to disable the normalisation as (in his words), it means 'wrong data'. This is true if the value is not a gauge or is a rate, but...
SteveStatistics: Posted by stevesh — Wed Oct 03, 2012 2:20 pm
]]>