As discussed in the issue, this adds both time fields and marks the TimeFlow field for eventual deprecation. The mentioned processing speed limitations do not appear to be a problem, see the following screenshot of the 99th percentile of goflow speed metrics from my monitoring.
I've tested NFv9 and am confident that IPFIX will work too, but I am unsure about the sFlow implementation. The latest two commits shave some bytes of a single flow message, but I am unsure about it, as TimeRecvd is the same anyways. It might be best to populate all three fields with the same value, or to leave both TimeFlow* empty.
Solves #22
As discussed in the issue, this adds both time fields and marks the
TimeFlow
field for eventual deprecation. The mentioned processing speed limitations do not appear to be a problem, see the following screenshot of the 99th percentile of goflow speed metrics from my monitoring.I've tested NFv9 and am confident that IPFIX will work too, but I am unsure about the sFlow implementation. The latest two commits shave some bytes of a single flow message, but I am unsure about it, as
TimeRecvd
is the same anyways. It might be best to populate all three fields with the same value, or to leave bothTimeFlow*
empty.