{"action":"created","issue":{"url":"https://api.github.com/repos/airbnb/airflow/issues/346","labels_url":"https://api.github.com/repos/airbnb/airflow/issues/346/labels{/name}","comments_url":"https://api.github.com/repos/airbnb/airflow/issues/346/comments","events_url":"https://api.github.com/repos/airbnb/airflow/issues/346/events","html_url":"https://github.com/airbnb/airflow/issues/346","id":104342436,"number":346,"title":"Alternative approach to log shipping","user":{"login":"RasterBurn","id":184899,"avatar_url":"https://avatars.githubusercontent.com/u/184899?v=3","gravatar_id":"","url":"https://api.github.com/users/RasterBurn","html_url":"https://github.com/RasterBurn","followers_url":"https://api.github.com/users/RasterBurn/followers","following_url":"https://api.github.com/users/RasterBurn/following{/other_user}","gists_url":"https://api.github.com/users/RasterBurn/gists{/gist_id}","starred_url":"https://api.github.com/users/RasterBurn/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/RasterBurn/subscriptions","organizations_url":"https://api.github.com/users/RasterBurn/orgs","repos_url":"https://api.github.com/users/RasterBurn/repos","events_url":"https://api.github.com/users/RasterBurn/events{/privacy}","received_events_url":"https://api.github.com/users/RasterBurn/received_events","type":"User","site_admin":false},"labels":[],"state":"open","locked":false,"assignee":null,"milestone":null,"comments":7,"created_at":"2015-09-01T19:59:43Z","updated_at":"2015-09-17T17:04:26Z","closed_at":null,"body":"Due to my network topology, I am unable to directly connect from the UI node to the worker nodes to retrieve logs.  I am running in a heroku-like environment, and internal hostnames are not routable and port numbers are randomized, so that makes the current system of sharing logs unusable for me.\r\n\r\nAre there any workarounds?  I think this might be a showstopper for adoption for me.\r\n\r\nI am just brainstorming here, but what if the worker nodes and the UI node all mounted a shared volume (NFS or Samba, for example), then the app code could just always check a local path for the log first, then fall back to the embedded webserver?"},"comment":{"url":"https://api.github.com/repos/airbnb/airflow/issues/comments/141151401","html_url":"https://github.com/airbnb/airflow/issues/346#issuecomment-141151401","issue_url":"https://api.github.com/repos/airbnb/airflow/issues/346","id":141151401,"user":{"login":"neovintage","id":2482,"avatar_url":"https://avatars.githubusercontent.com/u/2482?v=3","gravatar_id":"","url":"https://api.github.com/users/neovintage","html_url":"https://github.com/neovintage","followers_url":"https://api.github.com/users/neovintage/followers","following_url":"https://api.github.com/users/neovintage/following{/other_user}","gists_url":"https://api.github.com/users/neovintage/gists{/gist_id}","starred_url":"https://api.github.com/users/neovintage/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/neovintage/subscriptions","organizations_url":"https://api.github.com/users/neovintage/orgs","repos_url":"https://api.github.com/users/neovintage/repos","events_url":"https://api.github.com/users/neovintage/events{/privacy}","received_events_url":"https://api.github.com/users/neovintage/received_events","type":"User","site_admin":false},"created_at":"2015-09-17T17:04:26Z","updated_at":"2015-09-17T17:04:26Z","body":"@jlowin not yet. My initial thoughts were to use something like papertrail (https://papertrailapp.com) and have all the workers stream all of the logs there. I haven't had time to run a spike."}}