{"action":"created","issue":{"url":"https://api.github.com/repos/medic/medic-webapp/issues/2109","repository_url":"https://api.github.com/repos/medic/medic-webapp","labels_url":"https://api.github.com/repos/medic/medic-webapp/issues/2109/labels{/name}","comments_url":"https://api.github.com/repos/medic/medic-webapp/issues/2109/comments","events_url":"https://api.github.com/repos/medic/medic-webapp/issues/2109/events","html_url":"https://github.com/medic/medic-webapp/issues/2109","id":142270410,"number":2109,"title":"Babysitting SMSSync is a pain","user":{"login":"estellecomment","id":911434,"avatar_url":"https://avatars.githubusercontent.com/u/911434?v=3","gravatar_id":"","url":"https://api.github.com/users/estellecomment","html_url":"https://github.com/estellecomment","followers_url":"https://api.github.com/users/estellecomment/followers","following_url":"https://api.github.com/users/estellecomment/following{/other_user}","gists_url":"https://api.github.com/users/estellecomment/gists{/gist_id}","starred_url":"https://api.github.com/users/estellecomment/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/estellecomment/subscriptions","organizations_url":"https://api.github.com/users/estellecomment/orgs","repos_url":"https://api.github.com/users/estellecomment/repos","events_url":"https://api.github.com/users/estellecomment/events{/privacy}","received_events_url":"https://api.github.com/users/estellecomment/received_events","type":"User","site_admin":false},"labels":[{"url":"https://api.github.com/repos/medic/medic-webapp/labels/Priority","name":"Priority","color":"ff0022"},{"url":"https://api.github.com/repos/medic/medic-webapp/labels/Tech%20Leads","name":"Tech Leads","color":"bfe5bf"}],"state":"open","locked":false,"assignee":null,"milestone":null,"comments":5,"created_at":"2016-03-21T06:46:07Z","updated_at":"2016-03-21T22:42:13Z","closed_at":null,"body":"SMSSync is unreliable, and the tech leads have to nudge/restart it regularly, and end up carrying the gateways phone around and babysitting them. Not good.\r\n\r\nThis will eventually be solved by #1823 (messaging reliability), but I'm filing separately to keep track of Tech Lead pain specifically :)\r\nOur fork of SMSSync is behind, because SMSSync added some new features that our api wouldn't support (e.g. retrying the whole batch vs. only the failed messages)\r\n\r\nMeanwhile, I hear that @mandric has built some tips and tricks to help with the babysitting process? Documenting them all at the same place would be nice, if it's not already done.\r\n\r\n\r\n\r\n"},"comment":{"url":"https://api.github.com/repos/medic/medic-webapp/issues/comments/199521241","html_url":"https://github.com/medic/medic-webapp/issues/2109#issuecomment-199521241","issue_url":"https://api.github.com/repos/medic/medic-webapp/issues/2109","id":199521241,"user":{"login":"browndav","id":763977,"avatar_url":"https://avatars.githubusercontent.com/u/763977?v=3","gravatar_id":"","url":"https://api.github.com/users/browndav","html_url":"https://github.com/browndav","followers_url":"https://api.github.com/users/browndav/followers","following_url":"https://api.github.com/users/browndav/following{/other_user}","gists_url":"https://api.github.com/users/browndav/gists{/gist_id}","starred_url":"https://api.github.com/users/browndav/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/browndav/subscriptions","organizations_url":"https://api.github.com/users/browndav/orgs","repos_url":"https://api.github.com/users/browndav/repos","events_url":"https://api.github.com/users/browndav/events{/privacy}","received_events_url":"https://api.github.com/users/browndav/received_events","type":"User","site_admin":false},"created_at":"2016-03-21T22:42:13Z","updated_at":"2016-03-21T22:42:13Z","body":"The scope of the messaging reliability issue (#1823) , as I'm currently understanding it, is limited to (1) fixing defects in the `medic-transport` module, and (2) removing barriers to us upgrading SMSsync to the latest version. IMO it'd be good to do a synthetic test with the latest version of SMSsync, independent of our stack entirely, and see if there are still major defects. A couple organizations I know of have avoided SMSsync entirely after a technical analysis and ended up building their own tiny gateway app.\r\n\r\nTL;DR: if we believe SMSsync's latest version is now stable, IMO we should prove it. If problems remain, we should fix them before going too far down an SMSsync-specific refactoring path (on the theory that they represent the most technical risk)."}}