Skip to content

WIP: Now using event timestamp to retrieve relevant logs.#209

Open
mattatcha wants to merge 2 commits into
masterfrom
duplicate-logs
Open

WIP: Now using event timestamp to retrieve relevant logs.#209
mattatcha wants to merge 2 commits into
masterfrom
duplicate-logs

Conversation

@mattatcha

Copy link
Copy Markdown
Member

Using the event timestamp should prevent duplicate logs when a container restarts.

Comment thread router/pump.go
debug("pump.pumpLogs():", id, "ignored: environ ignore")
return
}
if !logDriverSupported(container) {

Copy link
Copy Markdown
Member

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.

Copy link
Copy Markdown
Member Author

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.

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"
@ebr

ebr commented Aug 28, 2016

Copy link
Copy Markdown
Contributor

How is it looking for getting this merged (without breaking the work done in #191)?
I'm between a rock and a hard place: would like to run master in hopes for a fix for #206, but I need to run my fork based on #201 in order to avoid duplication.

@michaelshobbs

Copy link
Copy Markdown
Member

@MattAitchison do you still want to pursue this route?

@mattatcha

Copy link
Copy Markdown
Member Author

@michaelshobbs yeah I do. I believe its a better route since it should prevent missing log output as described here.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

5 participants