consolidateBy doesn't seem to work properly

[Dieterbe]

demonstrated by nopzor in MT dashboard by looking at the chart for the incoming metrics.
Due to this being a counter, it might be special. I'm looking into it.

Confirmed so far by using fake data:

• consolidate by min/max/avg by selecting different archive seems to work fine (rollups, not runtime consol)
• runtime consolidation (only) seems to work fine
• both combined seems to work fine

TODO:

• check if it's different for counter, the specific metric in question

[Dieterbe]

yeah so the problem is that the metric is a counter, is which is derived via perSecond(), and we apply the consolidation in MT on the data before applying perSecond (wrong), in contrast to graphite which applies the consolidation later (right).

to make this a bit more visual, this is what the data looks like:

changing the consolidateBy in MT will just shift the line, basically, whether you take the mins of each bucket or the maxes at each bucket or the avgs of each bucket, from one bucket to the next, the delta will be about the same, IOW after perSecond it looks about the same.

this is very similar to / the same as #463