A common pattern I've seen has been to add a trivial http listener to your apps that responds to the /health endpoint, and have Aurora check that port rather than the non-http protocol port(s). For third-party code where it's not practical to do that, one might add a secondary process in the same task that performs protocol-specific health checking of your app, and reports the result on its own /health http listener.
On Mon, Nov 9, 2015 at 12:29 PM Dmitriy Shirchenko <cald...@gmail.com> wrote: > Hi everyone! > > As we are trying to adopt Aurora, one of the things we need is support for > health checking applications interacting via non-HTTP protocols. > > Has this been brought up before or can someone please give us guidance on > how to make this work? > > Thanks for your help, > Dmitriy! >
