You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I am using a really basic configuration and trying to use the timestamp_arrived primitive. It always produces a 0 value, either the start of epoch time or "0.0" if epoch timestamp is desired. This only seems to happen with sfacctd. Previously I was using timestamp_start in 1.5.2 and I do not see any issues with that aggregation primitive.
The text was updated successfully, but these errors were encountered:
… Improves timestamp_start, timestamp_end primitives and historical time-bins.
* fix, nfacctd: added support for timestamps via IPFIX IE #158 and #159 for historical time-bins.
I am using a really basic configuration and trying to use the timestamp_arrived primitive. It always produces a 0 value, either the start of epoch time or "0.0" if epoch timestamp is desired. This only seems to happen with sfacctd. Previously I was using timestamp_start in 1.5.2 and I do not see any issues with that aggregation primitive.
The text was updated successfully, but these errors were encountered: