From: Willy Tarreau Date: Fri, 25 Nov 2022 09:24:44 +0000 (+0100) Subject: DOC: config: mention that a single monitor-uri rule is supported X-Git-Tag: v2.7.0~35 X-Git-Url: http://git.ipfire.org/?a=commitdiff_plain;h=7fe0c62516ac0cb54290f8b6febe351038792e98;p=thirdparty%2Fhaproxy.git DOC: config: mention that a single monitor-uri rule is supported It was reported in issue #1059 that when multiple monitor-uri rules are specified, only the last one is used. While this was done on purpose since a single URI is used, it was not clearly mentioned in the doc, possibly leading to confusion or wasted time trying to establish a working setup. Let's clarify this point. --- diff --git a/doc/configuration.txt b/doc/configuration.txt index 3e8d5a6873..afe2498e7d 100644 --- a/doc/configuration.txt +++ b/doc/configuration.txt @@ -8526,7 +8526,9 @@ monitor-uri Monitor requests are processed very early, just after the request is parsed and even before any "http-request". The only rulesets applied before are the tcp-request ones. They cannot be logged either, and it is the intended - purpose. They are only used to report HAProxy's health to an upper component, + purpose. Only one URI may be configured for monitoring; when multiple + "monitor-uri" statements are present, the last one will define the URI to + be used. They are only used to report HAProxy's health to an upper component, nothing more. However, it is possible to add any number of conditions using "monitor fail" and ACLs so that the result can be adjusted to whatever check can be imagined (most often the number of available servers in a backend).