Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

timestamp_arrived fails to work for sfacctd #21

Closed
Jhors2 opened this issue Apr 15, 2016 · 2 comments
Closed

timestamp_arrived fails to work for sfacctd #21

Jhors2 opened this issue Apr 15, 2016 · 2 comments
Assignees
Labels

Comments

@Jhors2
Copy link

Jhors2 commented Apr 15, 2016

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.

@paololucente
Copy link
Member

Hi Jerred,

In 1.6.0 there has been already a fix around timestamp_arrival, see: b733eb4

Can you give a try to code in master and let me know if it works for you?

Cheers,
Paolo

@Jhors2
Copy link
Author

Jhors2 commented Apr 18, 2016

Seems to be fixed!
Thanks

@Jhors2 Jhors2 closed this as completed Apr 18, 2016
paololucente added a commit that referenced this issue Aug 31, 2016
… 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.
@paololucente paololucente self-assigned this Nov 7, 2016
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

2 participants