{"action":"opened","issue":{"url":"https://api.github.com/repos/timberio/docs/issues/20","repository_url":"https://api.github.com/repos/timberio/docs","labels_url":"https://api.github.com/repos/timberio/docs/issues/20/labels{/name}","comments_url":"https://api.github.com/repos/timberio/docs/issues/20/comments","events_url":"https://api.github.com/repos/timberio/docs/issues/20/events","html_url":"https://github.com/timberio/docs/issues/20","id":340328472,"node_id":"MDU6SXNzdWUzNDAzMjg0NzI=","number":20,"title":"Add documentation for the cause of L10, specifically on the Heroku side","user":{"login":"binarylogic","id":1663286,"node_id":"MDQ6VXNlcjE2NjMyODY=","avatar_url":"https://avatars1.githubusercontent.com/u/1663286?v=4","gravatar_id":"","url":"https://api.github.com/users/binarylogic","html_url":"https://github.com/binarylogic","followers_url":"https://api.github.com/users/binarylogic/followers","following_url":"https://api.github.com/users/binarylogic/following{/other_user}","gists_url":"https://api.github.com/users/binarylogic/gists{/gist_id}","starred_url":"https://api.github.com/users/binarylogic/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/binarylogic/subscriptions","organizations_url":"https://api.github.com/users/binarylogic/orgs","repos_url":"https://api.github.com/users/binarylogic/repos","events_url":"https://api.github.com/users/binarylogic/events{/privacy}","received_events_url":"https://api.github.com/users/binarylogic/received_events","type":"User","site_admin":false},"labels":[],"state":"open","locked":false,"assignee":null,"assignees":[],"milestone":null,"comments":0,"created_at":"2018-07-11T17:02:52Z","updated_at":"2018-07-11T17:02:52Z","closed_at":null,"author_association":"MEMBER","body":"In the Heroku [docs](https://devcenter.heroku.com/articles/error-codes#l10-drain-buffer-overflow):\n\n> Another common cause of L10 error messages is a sudden burst of log messages from a dyno. As each line of dyno output (e.g. a line of a stack trace) is a single log message, and Logplex limits the total number of un-transmitted log messages it will keep in memory to 1024 messages, a burst of lines from a dyno can overflow buffers in Logplex. In order to allow the log stream to catch up, Logplex will discard messages where necessary, keeping newer messages in favor of older ones.\n\nThis says the error can happen entirely on the Heroku side. We need to make sure our customers are aware of this because the top-level description of the error points the finger at us when we are not the issue."}}
{"actor":{"display_login":"binarylogic"}}