Update the Logstash to Logstash Native doc to reflect the multiple ho…

…sts usage. (#15512) * Update the Logstash to Logstash Native doc to reflect the multiple hosts usage. * Logstash to Logstash comm page, adding LS-to-LS native HA support. * Apply suggestions from code review Refining the context. Co-authored-by: Andres Rodriguez <[email protected]> --------- Co-authored-by: Andres Rodriguez <[email protected]>
elastic · Nov 6, 2023 · fa1382f · fa1382f
1 parent 51886b9
commit fa1382f
Show file tree

Hide file tree

Showing 2 changed files with 4 additions and 5 deletions.
diff --git a/docs/static/ls-ls-config.asciidoc b/docs/static/ls-ls-config.asciidoc
@@ -18,8 +18,7 @@ Logstash-to-Logstash communication can be achieved in one of two ways:
 This is the preferred method to implement Logstash-to-Logstash. It replaces <<ls-to-ls-http>> and has these considerations:
 
 * It relies on HTTP as the communication protocol between the Input and Output.
-* It does not provide built-in high availability. You will need to implement your own load balancer in between the Logstash output and the Logstash input.
-* If you need a proxy between the Logstash instances, you can use any HTTP proxy.
+* It supports multiple hosts, providing high availability by load balancing equally amongst the multiple destination hosts.
 * No connection information is added to events.
 
 Ready to see more configuration details? See <<ls-to-ls-native>>.

diff --git a/docs/static/ls-ls-native.asciidoc b/docs/static/ls-ls-native.asciidoc
@@ -36,15 +36,15 @@ input {
 
 In order to obtain the best performance when sending data from one Logstash to another, the data is batched and compressed. As such, the upstream Logstash (the sending Logstash) only needs to be concerned about configuring the receiving endpoint with these options:
 
-* `hosts` - The receiving Logstash and port. If no port specified, 9800 will be used.
+* `hosts` - The receiving one or more Logstash host and port pairs. If no port specified, 9800 will be used.
 
-NOTE: In the future, {ls} will support multiple output hosts.
+NOTE: {ls} load balances batched events to _all_ of its configured downstream hosts. Any failures caused by network issues, back-pressure or other conditions, will result in the downstream host being isolated from load balancing for at least 60 seconds.
 
 [source,json]
 ----
 output {
     logstash {
-        hosts => '10.0.0.123:9800'
+        hosts => ["10.0.0.123", "10.0.1.123:9800"]
     }
 }
 ----