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

No milisecond on timestamps causes log ordering issues #444

Open
yunusemrecatalcam opened this issue Dec 9, 2019 · 3 comments · May be fixed by #382
Open

No milisecond on timestamps causes log ordering issues #444

yunusemrecatalcam opened this issue Dec 9, 2019 · 3 comments · May be fixed by #382
Labels
status: fix-provided type: enhancement

Comments

@yunusemrecatalcam
Copy link

yunusemrecatalcam commented Dec 9, 2019 •
edited

Hi, I've commented to related PR chat but couldn't get an answer so I'm asking from there.
#401 (comment)

Since log messages doesn't includes miliseconds in timestamp fields, observing exceptions is so hard. Is there a parameter or something for getting timestamps from docker logs. It really hurts us and feels weird that only a few person talks about this issue, am I missing something?
@osencan
Copy link

osencan commented Dec 16, 2019

I have faced the same problem here. Are there any solutions or workarounds found yet?

@michaelshobbs
Copy link
Member

related PR: #382

@michaelshobbs michaelshobbs linked a pull request May 4, 2020 that will close this issue
Sub-second accuracy in syslog adapter #382
Open
@prem-winzo
Copy link

Are we doing anything to solve this?

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

Successfully merging a pull request may close this issue.

Sub-second accuracy in syslog adapter romanlevin/logspout
4 participants
@michaelshobbs @osencan @yunusemrecatalcam @prem-winzo