When viewing app flows within a device, the default column sorting for inboundbitrate and outboundbitrate are correct. If you click on either column to sort ascending/descending by that column, the sort ignores the unit of measure and only sorts by the numeric value. This can result in 930 bps being listed above 1.4 kbps.
Hi Brian, in what version of LiveNX are you encountering this behavior? I am unable to replicate this in the Flow Table or reports in my 6.1.2 lab.
Sorry about the long delay. My account got messed up and I couldn’t see or respond to ANY questions in the forums.
We are using LiveNX 6.1.0-20170331-71c4c7d
Now we are on 6.2.0 and the sort is still not respecting the unit of measure..
if the sort order is not specified for any column, then the inbound/outbound bit rate columns are sorted correctly. If you change the sort to descending, then the UOM is ignored, only the numeric values are used.