From: Aurelien DARRAGON <adarragon@haproxy.com>
Date: Tue, 17 Dec 2024 10:54:06 +0000 (+0100)
Subject: DOC: config: add example for server "track" keyword
X-Git-Tag: v3.0.8~45
X-Git-Url: http://git.haproxy.org/?a=commitdiff_plain;h=b2dde3f90fc8b3cc617d3be946fdc08734503063;p=haproxy-3.0.git

DOC: config: add example for server "track" keyword

As requested on GH #2325, "track" server keyword could benefit from a
simple config example to show how to make use of it.

That's what we're doing in this commit, thanks to GH user @HAkmiller
for the suggestion.

(cherry picked from commit 48545113f4db86ad43a99ba01742a9811410e6dc)
Signed-off-by: Christopher Faulet <cfaulet@haproxy.com>
(cherry picked from commit d270bc5864a3cec0b5faf40ae8ca9db0a365da81)
Signed-off-by: Christopher Faulet <cfaulet@haproxy.com>
---

diff --git a/doc/configuration.txt b/doc/configuration.txt
index ccd2a01..5b62244 100644
--- a/doc/configuration.txt
+++ b/doc/configuration.txt
@@ -18284,6 +18284,15 @@ track [<backend>/]<server>
   enabled. If <backend> is omitted the current one is used. If disable-on-404 is
   used, it has to be enabled on both proxies.
 
+  Example :
+
+    backend A
+    server a1 1.1.1.1:80 track B/b1
+    server a2 1.1.1.2:80 track B/b1
+
+    backend B
+    server b1 2.2.2.2:80 check
+
 tls-tickets
   May be used in the following contexts: tcp, http, log, peers, ring