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.

Sign up for GitHub

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

Jump to bottom

Limitation: accuracy only goes to seconds #14

Closed
dogoncouch opened this issue Mar 6, 2017 · 1 comment
Closed

Limitation: accuracy only goes to seconds #14

dogoncouch opened this issue Mar 6, 2017 · 1 comment

Comments

@dogoncouch
Copy link
Owner

Because syslog timestamps don't have milliseconds, sorting after a merge is only accurate to the nearest second. Entries from each file for each second will be lumped together.
@dogoncouch
Copy link
Owner Author

The syslogiso parser can handle fractions of seconds, if the timestamps provide them. The tcpdump parser can, too.

The sort_time() method of LogData objects will use fractions of seconds to sort, if available.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@dogoncouch