http://wiki.nginx.org/index.php?title=HttpHealthcheckModule&feed=atom&action=history 2013-05-19T06:35:19Z Revision history for this page on the wiki MediaWiki 1.19.0 http://wiki.nginx.org/index.php?title=HttpHealthcheckModule&diff=473&oldid=prev 2010-09-22T19:26:18Z

<p>moved <a href="/NginxHttpHealthcheckModule" class="mw-redirect" title="NginxHttpHealthcheckModule">NginxHttpHealthcheckModule</a> to <a href="/HttpHealthcheckModule" title="HttpHealthcheckModule">HttpHealthcheckModule</a>: Removing Nginx prefix from page titles</p> <p><b>New page</b></p><div>= ngx_http_healthcheck_module =<br /> <br /> ''This module is not distributed with the Nginx source. Installation instructions are below. You can get the module [http://github.com/cep21/healthcheck_nginx_upstreams here]''<br /> <br /> Healthcheck plugin for nginx. It polls backends and if they respond with<br /> HTTP 200 + an optional request body, they are marked good. Otherwise, they<br /> are marked bad.<br /> <br /> Note this also gives you access to a health status page that lets you see<br /> how well your healthcheck are doing.<br /> <br /> The docs on this wiki can get out of date. For the authoritative information, please see the README file inside the plugin's [http://github.com/cep21/healthcheck_nginx_upstreams git repository].<br /> <br /> == Directives ==<br /> <br /> === healthcheck_enabled ===<br /> '''syntax''' ''healthcheck_enabled''<br /> <br /> '''context''' ''upstream''<br /> <br /> Enables health checking of an upstream<br /> <br /> === healthcheck_delay ===<br /> '''syntax''' ''healthcheck_delay''<br /> <br /> '''default''' ''10000''<br /> <br /> '''context''' ''upstream''<br /> <br /> Delay in msec between healthchecks for a single peer.<br /> <br /> === healthcheck_timeout ===<br /> '''syntax''' ''healthcheck_timeout''<br /> <br /> '''default''' ''2000''<br /> <br /> '''context''' ''upstream''<br /> <br /> How long in msec a healthcheck is allowed to take place<br /> <br /> === healthcheck_failcount ===<br /> '''syntax''' ''healthcheck_failcount''<br /> <br /> '''default''' ''2''<br /> <br /> '''context''' ''upstream''<br /> <br /> Number of healthchecks good or bad in a row it takes to switch from down to up and back. Good to prevent flapping<br /> <br /> === healthcheck_send ===<br /> '''syntax''' ''healthcheck_send''<br /> <br /> '''default''' ''&lt;empty&gt;''<br /> <br /> '''context''' ''upstream''<br /> <br /> Required directive. What to send for the healthcheck. Each argument is appended by \r\n and the entire thing is suffixed with another \r\n. For example:<br /> <br /> &lt;geshi lang=&quot;nginx&quot;&gt;<br /> healthcheck_send 'GET /health HTTP/1.0'<br /> 'Host: www.yourhost.com';<br /> &lt;/geshi&gt;<br /> <br /> Note that you probably want to end your health check with some directive that closes the connection, like Connection: close.<br /> <br /> === healthcheck_expected ===<br /> '''syntax''' ''healthcheck_expected''<br /> <br /> '''default''' ''&lt;UNSET&gt;''<br /> <br /> '''context''' ''upstream''<br /> <br /> What to expect in the HTTP BODY, (meaning not the headers), in a correct response. If unset, just a HTTP 200 status code is required for a peer<br /> <br /> === healthcheck_buffer ===<br /> '''syntax''' ''healthcheck_buffer''<br /> <br /> '''default''' ''1000''<br /> <br /> '''context''' ''upstream''<br /> <br /> How big a buffer to use for the health check. Remember to include headers PLUS body, not just body.<br /> <br /> === healthcheck_status ===<br /> '''syntax''' ''healthcheck_status''<br /> <br /> '''context''' ''upstream''<br /> <br /> When inside a /location block, replaced the HTTP body with backend health status. Use similarly to the stub_status module.<br /> <br /> == Installation ==<br /> <br /> This module is not distributed with the Nginx source. You can download the module from [http://github.com/cep21/healthcheck_nginx_upstreams here]. Read the installation instructions inside the README file.<br /> <br /> == Bugs ==<br /> <br /> Please report bugs to [http://github.com/cep21/healthcheck_nginx_upstreams/issues here]</div>

MichaelLustfield