{"action":"created","issue":{"url":"https://api.github.com/repos/vsivsi/meteor-job-collection/issues/147","labels_url":"https://api.github.com/repos/vsivsi/meteor-job-collection/issues/147/labels{/name}","comments_url":"https://api.github.com/repos/vsivsi/meteor-job-collection/issues/147/comments","events_url":"https://api.github.com/repos/vsivsi/meteor-job-collection/issues/147/events","html_url":"https://github.com/vsivsi/meteor-job-collection/issues/147","id":126826920,"number":147,"title":"Is there any alternative to logging job output?","user":{"login":"a4xrbj1","id":13525267,"avatar_url":"https://avatars.githubusercontent.com/u/13525267?v=3","gravatar_id":"","url":"https://api.github.com/users/a4xrbj1","html_url":"https://github.com/a4xrbj1","followers_url":"https://api.github.com/users/a4xrbj1/followers","following_url":"https://api.github.com/users/a4xrbj1/following{/other_user}","gists_url":"https://api.github.com/users/a4xrbj1/gists{/gist_id}","starred_url":"https://api.github.com/users/a4xrbj1/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/a4xrbj1/subscriptions","organizations_url":"https://api.github.com/users/a4xrbj1/orgs","repos_url":"https://api.github.com/users/a4xrbj1/repos","events_url":"https://api.github.com/users/a4xrbj1/events{/privacy}","received_events_url":"https://api.github.com/users/a4xrbj1/received_events","type":"User","site_admin":false},"labels":[],"state":"open","locked":false,"assignee":null,"milestone":null,"comments":3,"created_at":"2016-01-15T08:18:31Z","updated_at":"2016-01-19T12:30:44Z","closed_at":null,"body":"Hi Vaughn,\r\n\r\nI checked this issue: https://github.com/vsivsi/meteor-job-collection/issues/21 but I don't understand the solution. I want to avoid clogging up my console on development with the standard:\r\n\r\n    // Log everything to stdout\r\n    myJobs.setLogStream(process.stdout);\r\n\r\nand instead would like to write it to a local file.\r\n\r\nAlso, how are others running the log on the production apps? The output of the job worker is important to find errors, especially in production.\r\n\r\nApart from this professional solution (https://www.loggly.com), what are people using?"},"comment":{"url":"https://api.github.com/repos/vsivsi/meteor-job-collection/issues/comments/172837403","html_url":"https://github.com/vsivsi/meteor-job-collection/issues/147#issuecomment-172837403","issue_url":"https://api.github.com/repos/vsivsi/meteor-job-collection/issues/147","id":172837403,"user":{"login":"rhyslbw","id":303881,"avatar_url":"https://avatars.githubusercontent.com/u/303881?v=3","gravatar_id":"","url":"https://api.github.com/users/rhyslbw","html_url":"https://github.com/rhyslbw","followers_url":"https://api.github.com/users/rhyslbw/followers","following_url":"https://api.github.com/users/rhyslbw/following{/other_user}","gists_url":"https://api.github.com/users/rhyslbw/gists{/gist_id}","starred_url":"https://api.github.com/users/rhyslbw/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/rhyslbw/subscriptions","organizations_url":"https://api.github.com/users/rhyslbw/orgs","repos_url":"https://api.github.com/users/rhyslbw/repos","events_url":"https://api.github.com/users/rhyslbw/events{/privacy}","received_events_url":"https://api.github.com/users/rhyslbw/received_events","type":"User","site_admin":false},"created_at":"2016-01-19T12:30:44Z","updated_at":"2016-01-19T12:30:44Z","body":"You can easily get access to the same data by subscribing the the `call` event, then remove `myJobs.setLogStream(process.stdout)`. I just did a quick search on Atmosphere, and it looks like this should be a simple way to dump the logs to a file https://atmospherejs.com/ostrio/loggerfile"}}