Just wondering if the lack of choices for preprocessing on items is by design? I'd love to be able to do a custom arithmetic operation ...
Specifically, I am trying to calculate link utilization % on a network interface on the fly...
I am aware I can create a calculated item based on the last() value of raw bitrate data on the interface... But last() is usually a representation of data from a previous data collection (the calculated item's timing is not in sync w/ the raw data item) ... So the utilization % ends up not being 'real-time' and doesn't match the raw throughput data.
I'm guessing this is done on purpose for performance reasons, but wondering if that is really the case or if it is a feature planned for the future.. Or am I missing some other method I can use to get the data in sync?
Specifically, I am trying to calculate link utilization % on a network interface on the fly...
I am aware I can create a calculated item based on the last() value of raw bitrate data on the interface... But last() is usually a representation of data from a previous data collection (the calculated item's timing is not in sync w/ the raw data item) ... So the utilization % ends up not being 'real-time' and doesn't match the raw throughput data.
I'm guessing this is done on purpose for performance reasons, but wondering if that is really the case or if it is a feature planned for the future.. Or am I missing some other method I can use to get the data in sync?