{"action":"created","issue":{"url":"https://api.github.com/repos/gliderlabs/logspout/issues/207","repository_url":"https://api.github.com/repos/gliderlabs/logspout","labels_url":"https://api.github.com/repos/gliderlabs/logspout/issues/207/labels{/name}","comments_url":"https://api.github.com/repos/gliderlabs/logspout/issues/207/comments","events_url":"https://api.github.com/repos/gliderlabs/logspout/issues/207/events","html_url":"https://github.com/gliderlabs/logspout/issues/207","id":164106783,"number":207,"title":"Is there a health check of any kind on logspout??","user":{"login":"326TimesBetter","id":16246896,"avatar_url":"https://avatars.githubusercontent.com/u/16246896?v=3","gravatar_id":"","url":"https://api.github.com/users/326TimesBetter","html_url":"https://github.com/326TimesBetter","followers_url":"https://api.github.com/users/326TimesBetter/followers","following_url":"https://api.github.com/users/326TimesBetter/following{/other_user}","gists_url":"https://api.github.com/users/326TimesBetter/gists{/gist_id}","starred_url":"https://api.github.com/users/326TimesBetter/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/326TimesBetter/subscriptions","organizations_url":"https://api.github.com/users/326TimesBetter/orgs","repos_url":"https://api.github.com/users/326TimesBetter/repos","events_url":"https://api.github.com/users/326TimesBetter/events{/privacy}","received_events_url":"https://api.github.com/users/326TimesBetter/received_events","type":"User","site_admin":false},"labels":[],"state":"open","locked":false,"assignee":null,"assignees":[],"milestone":null,"comments":16,"created_at":"2016-07-06T15:39:40Z","updated_at":"2016-09-08T22:01:10Z","closed_at":null,"body":"I have logspout set to publish its logs to a port, and typically I can view its output by curling that port, however I am currently getting no response. If I restart the container, it will typically solve this problem, but I'm trying to find a root cause. Is there a way to health check an existing logspout container to see why it is not responding before I restart it??"},"comment":{"url":"https://api.github.com/repos/gliderlabs/logspout/issues/comments/245755608","html_url":"https://github.com/gliderlabs/logspout/issues/207#issuecomment-245755608","issue_url":"https://api.github.com/repos/gliderlabs/logspout/issues/207","id":245755608,"user":{"login":"ebr","id":2433541,"avatar_url":"https://avatars.githubusercontent.com/u/2433541?v=3","gravatar_id":"","url":"https://api.github.com/users/ebr","html_url":"https://github.com/ebr","followers_url":"https://api.github.com/users/ebr/followers","following_url":"https://api.github.com/users/ebr/following{/other_user}","gists_url":"https://api.github.com/users/ebr/gists{/gist_id}","starred_url":"https://api.github.com/users/ebr/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/ebr/subscriptions","organizations_url":"https://api.github.com/users/ebr/orgs","repos_url":"https://api.github.com/users/ebr/repos","events_url":"https://api.github.com/users/ebr/events{/privacy}","received_events_url":"https://api.github.com/users/ebr/received_events","type":"User","site_admin":false},"created_at":"2016-09-08T22:01:10Z","updated_at":"2016-09-08T22:01:10Z","body":"From struggling with suddenly missing logs for the past several weeks, I'm quite sure at least one of the causes is log rotation when using the `json-file` driver. we switched to `journald` logging driver for docker, and the issue went away.\r\n\r\n@edude03 give the `brodsky/logspout:latest` fork a try until #201 is merged - it's essentially a build of #201, which I just rebased."}}
{"actor":{"display_login":"ebr"}}