Just as a reference you could look at some of the connection tests that Monit
allows:

https://mmonit.com/monit/documentation/monit.html#CONNECTION-TESTING

Obviously there are quite a few there so it might go well beyond what's
reasonable for container health checking.

I think to meet our use cases the addition of the HTTP check already
mentioned would be sufficient but to add to it, I could imagine that it
might be useful to be able to specify a regular expression to search for in
the returned HTML instead of or in addition to the status code.

Also, since you guys are expanding into offer TCP routing for containers, a
generic TCP monitor that looked for a specific regular expression in the
returned data might be useful, which might also require specifying data to
send to trigger a response.

Aaron



--
View this message in context: http://cf-dev.70369.x6.nabble.com/cf-dev-Richer-health-checks-for-CF-apps-request-for-use-cases-tp3676p3677.html
Sent from the CF Dev mailing list archive at Nabble.com.