-
Notifications
You must be signed in to change notification settings - Fork 680
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
WIP: Now using event timestamp to retrieve relevant logs. #209
base: master
Are you sure you want to change the base?
Conversation
@@ -153,67 +153,25 @@ func (p *LogsPump) pumpLogs(event *docker.APIEvents, backlog bool) { | |||
debug("pump.pumpLogs():", id, "ignored: environ ignore") | |||
return | |||
} | |||
if !logDriverSupported(container) { |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This drops the following functionality 324db6e.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Damn it. I didn't mean to remove that commit.
d665381
to
357e669
Compare
trying to hit /logs for a container that does not support that endpoint results in the following error in that container's stdout "Error running logs job: configured logging reader does not support reading"
@MattAitchison do you still want to pursue this route? |
@michaelshobbs yeah I do. I believe its a better route since it should prevent missing log output as described here. |
Using the event timestamp should prevent duplicate logs when a container restarts.