{"action":"opened","issue":{"url":"https://api.github.com/repos/heroku/log-shuttle/issues/42","labels_url":"https://api.github.com/repos/heroku/log-shuttle/issues/42/labels{/name}","comments_url":"https://api.github.com/repos/heroku/log-shuttle/issues/42/comments","events_url":"https://api.github.com/repos/heroku/log-shuttle/issues/42/events","html_url":"https://github.com/heroku/log-shuttle/issues/42","id":55343377,"number":42,"title":"Disordered Logs","user":{"login":"trestletech","id":1593639,"avatar_url":"https://avatars.githubusercontent.com/u/1593639?v=3","gravatar_id":"","url":"https://api.github.com/users/trestletech","html_url":"https://github.com/trestletech","followers_url":"https://api.github.com/users/trestletech/followers","following_url":"https://api.github.com/users/trestletech/following{/other_user}","gists_url":"https://api.github.com/users/trestletech/gists{/gist_id}","starred_url":"https://api.github.com/users/trestletech/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/trestletech/subscriptions","organizations_url":"https://api.github.com/users/trestletech/orgs","repos_url":"https://api.github.com/users/trestletech/repos","events_url":"https://api.github.com/users/trestletech/events{/privacy}","received_events_url":"https://api.github.com/users/trestletech/received_events","type":"User","site_admin":false},"labels":[],"state":"open","locked":false,"assignee":null,"milestone":null,"comments":0,"created_at":"2015-01-23T22:50:58Z","updated_at":"2015-01-23T22:50:58Z","closed_at":null,"body":"Hi. We're getting a rearrangement of our logs when we view them in Logplex. (Note the timestamps)\r\n\r\n```\r\n2015-01-23T21:58:24.342756+00:00 shinyapps[shuttle]: SEND {\r\n2015-01-23T21:58:24.336726+00:00 shinyapps[shuttle]: \"values\": \"\\\"domain\\\"\\n293.052725\\n1627.343375\" \r\n2015-01-23T21:58:24.338810+00:00 shinyapps[shuttle]:  \"name\": \"scale/y\",\r\n2015-01-23T21:58:24.343985+00:00 shinyapps[shuttle]: \"inputMessages\": [] \r\n2015-01-23T21:58:24.343986+00:00 shinyapps[shuttle]: }\r\n2015-01-23T21:58:24.340089+00:00 shinyapps[shuttle]: \"command\": \"update\" \r\n2015-01-23T21:58:24.338812+00:00 shinyapps[shuttle]:  \"type\": \"csv\",\r\n2015-01-23T21:58:24.340087+00:00 shinyapps[shuttle]:  \"ggvis_command\": {\r\n2015-01-23T21:58:24.342760+00:00 shinyapps[shuttle]:  \"plotId\": \"BarPlot\",\r\n2015-01-23T21:58:24.342758+00:00 shinyapps[shuttle]:  \"custom\": {\r\n2015-01-23T21:58:24.343981+00:00 shinyapps[shuttle]:  \"TSTitle\": \"<i>Accommodation</i> tourist spend in Auckland\",\r\n2015-01-23T21:58:24.338791+00:00 shinyapps[shuttle]:  \"plotId\": \"BarPlot\",\r\n2015-01-23T21:58:24.338818+00:00 shinyapps[shuttle]: } \r\n2015-01-23T21:58:24.341426+00:00 shinyapps[shuttle]: \"command\": \"update\" \r\n2015-01-23T21:58:24.338820+00:00 shinyapps[shuttle]: }\r\n2015-01-23T21:58:24.341428+00:00 shinyapps[shuttle]: } \r\n2015-01-23T21:58:24.343979+00:00 shinyapps[shuttle]:  \"errors\": [],\r\n2015-01-23T21:58:24.343980+00:00 shinyapps[shuttle]: \"values\": {\r\n2015-01-23T21:58:24.338817+00:00 shinyapps[shuttle]: ] \r\n2015-01-23T21:58:24.340088+00:00 shinyapps[shuttle]:  \"plotId\": \"TSPlot\",\r\n2015-01-23T21:58:24.342762+00:00 shinyapps[shuttle]: } \r\n2015-01-23T21:58:24.341425+00:00 shinyapps[shuttle]:  \"plotId\": \"Map\",\r\n2015-01-23T21:58:24.343977+00:00 shinyapps[shuttle]: SEND {\r\n2015-01-23T21:58:24.340092+00:00 shinyapps[shuttle]: }\r\n2015-01-23T21:58:24.341429+00:00 shinyapps[shuttle]: }\r\n2015-01-23T21:58:24.342764+00:00 shinyapps[shuttle]: }\r\n2015-01-23T21:58:24.342759+00:00 shinyapps[shuttle]:  \"ggvis_command\": {\r\n2015-01-23T21:58:24.343984+00:00 shinyapps[shuttle]: },\r\n2015-01-23T21:58:24.343983+00:00 shinyapps[shuttle]: \"BarTitle\": \"Product distribution of tourism spend in Auckland\" \r\n```\r\n\r\nI'm under the impression that log shuttle is merely sending unordered HTTP requests, so perhaps this is expected with a series of rapid-fire requests like this. \r\n\r\nFor our use case, however, we expect rapid bursts of logging, but not necessarily long periods of heavy log writing. Is it possible to tune the configuration (e.g. using only 1 \"Batcher\" or \"Outlet\") to increase the likelihood that logs get through in order? \r\n\r\nEven if there's not a recommended best practice, I'm happy to try out whatever hypotheses you think might help.\r\n\r\nThanks!"}}