Http upstream check
tengine.taobao.org
tengine.taobao.org
Compare, for example, this:
https://www.exratione.com/2012/12/websockets-over-ssl-haprox...
With this:
https://www.exratione.com/2013/06/websockets-over-ssl-with-n...
Keep in mind that the "heavier duty" the health check, the less frequently it can be run at scale.
edit: The best clue is probably the phrase "available as part of our commercial subscription only" appearing all over the upstream module documentation.[0]
[0] http://nginx.org/en/docs/http/ngx_http_upstream_module.html
1. Listen on UNIX socket only 2. Bind TCP socket to localhost only 3. Bind TCP socket and port, cut off connections at firewall level
If you write your software with a dedicated healthcheck url, it's much more robust because you can test all critical functionality with that helthcheck (just make sure you block access to it from the outside otherwise someone has a really easy way to DDOS you!).