{"action":"created","issue":{"url":"https://api.github.com/repos/istresearch/traptor/issues/56","repository_url":"https://api.github.com/repos/istresearch/traptor","labels_url":"https://api.github.com/repos/istresearch/traptor/issues/56/labels{/name}","comments_url":"https://api.github.com/repos/istresearch/traptor/issues/56/comments","events_url":"https://api.github.com/repos/istresearch/traptor/issues/56/events","html_url":"https://github.com/istresearch/traptor/issues/56","id":194649745,"number":56,"title":"Logs should be written to docker logs, not mounted files","user":{"login":"joequery","id":503584,"avatar_url":"https://avatars.githubusercontent.com/u/503584?v=3","gravatar_id":"","url":"https://api.github.com/users/joequery","html_url":"https://github.com/joequery","followers_url":"https://api.github.com/users/joequery/followers","following_url":"https://api.github.com/users/joequery/following{/other_user}","gists_url":"https://api.github.com/users/joequery/gists{/gist_id}","starred_url":"https://api.github.com/users/joequery/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/joequery/subscriptions","organizations_url":"https://api.github.com/users/joequery/orgs","repos_url":"https://api.github.com/users/joequery/repos","events_url":"https://api.github.com/users/joequery/events{/privacy}","received_events_url":"https://api.github.com/users/joequery/received_events","type":"User","site_admin":false},"labels":[{"id":252904298,"url":"https://api.github.com/repos/istresearch/traptor/labels/enhancement","name":"enhancement","color":"84b6eb","default":true}],"state":"open","locked":false,"assignee":null,"assignees":[],"milestone":null,"comments":2,"created_at":"2016-12-09T17:15:58Z","updated_at":"2016-12-09T19:44:59Z","closed_at":null,"body":"Following docker best practices, application logs should not write to a mounted log. Not only does this go against docker conventions, additional IO overhead can be incurred using the mounted volumes - especially for an application like Traptor that logs so often.\r\n\r\nTraptor should instead log to `/dev/stdout` and `/dev/stderr`. I believe this is probably a simple config/environment variable change.\r\n\r\nDocker uses the container stdout and stderr for the `$ docker logs` command in addition to the overall built-in logging driver. Using the built-in logging driver will also make it trivial to transition to a logger service like CloudWatch/splunk in the future."},"comment":{"url":"https://api.github.com/repos/istresearch/traptor/issues/comments/266104634","html_url":"https://github.com/istresearch/traptor/issues/56#issuecomment-266104634","issue_url":"https://api.github.com/repos/istresearch/traptor/issues/56","id":266104634,"user":{"login":"madisonb","id":3504194,"avatar_url":"https://avatars.githubusercontent.com/u/3504194?v=3","gravatar_id":"","url":"https://api.github.com/users/madisonb","html_url":"https://github.com/madisonb","followers_url":"https://api.github.com/users/madisonb/followers","following_url":"https://api.github.com/users/madisonb/following{/other_user}","gists_url":"https://api.github.com/users/madisonb/gists{/gist_id}","starred_url":"https://api.github.com/users/madisonb/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/madisonb/subscriptions","organizations_url":"https://api.github.com/users/madisonb/orgs","repos_url":"https://api.github.com/users/madisonb/repos","events_url":"https://api.github.com/users/madisonb/events{/privacy}","received_events_url":"https://api.github.com/users/madisonb/received_events","type":"User","site_admin":false},"created_at":"2016-12-09T19:44:59Z","updated_at":"2016-12-09T19:44:59Z","body":"Can you reference how this works or provide an example of this setup working with an ELK stack? It's trivial to change logging from a file to stdout, but we had issues then with logging and monitoring when trying to hook Logstash into the container logs. "}}
{"actor":{"display_login":"madisonb"}}