Thanks for your responses!
Is there any philosophical opposition to adding support for arbitrary
health check shell out commands to be run as part of health checking? Ie
allowing someone to specify a command line out instead of an HTTP endpoint?
If not, then I would love to take a crack and submit
The upside to what Ben described above is that you can then still handle
the graceful teardown in the way that best suits your application.
On Mon, Nov 9, 2015 at 12:40 PM, ben...@gmail.com wrote:
> A common pattern I've seen has been to add a trivial http listener to your
> apps that responds t
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
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!
