Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Update the Logstash to Logstash Native doc to reflect the multiple hosts usage. #15512

Merged
merged 3 commits into from
Nov 6, 2023
Merged

Update the Logstash to Logstash Native doc to reflect the multiple hosts usage. #15512

Show file tree
Hide file tree
Changes from 2 commits
Commits
Show all changes
3 commits
Select commit Hold shift + click to select a range
70813bf
Update the Logstash to Logstash Native doc to reflect the multiple ho…
mashhurs Oct 27, 2023
eb289f9
Logstash to Logstash comm page, adding LS-to-LS native HA support.
mashhurs Oct 27, 2023
a929535
Apply suggestions from code review
mashhurs Oct 31, 2023
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Jump to
Jump to file
Failed to load files.
Diff view
Diff view
2 changes: 1 addition & 1 deletion docs/static/ls-ls-config.asciidoc
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -18,7 +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.
* It provides built-in _fairness_ load balancing, which, distributes batch of events to a downstream that is running, has a capacity to receive events and no recent failures.
mashhurs marked this conversation as resolved.
Show resolved Hide resolved
mashhurs marked this conversation as resolved.
Show resolved Hide resolved
* If you need a proxy between the Logstash instances, you can use any HTTP proxy.
mashhurs marked this conversation as resolved.
Show resolved Hide resolved
mashhurs marked this conversation as resolved.
Show resolved Hide resolved
* No connection information is added to events.

Expand Down
6 changes: 2 additions & 4 deletions docs/static/ls-ls-native.asciidoc
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -36,15 +36,13 @@ 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.

NOTE: In the future, {ls} will support multiple output hosts.
mashhurs marked this conversation as resolved.
Show resolved Hide resolved
* `hosts` - The receiving Logstash host and port pairs. If no port specified, 9800 will be used.
mashhurs marked this conversation as resolved.
Show resolved Hide resolved

[source,json]
----
output {
logstash {
hosts => '10.0.0.123:9800'
hosts => ["10.0.0.123", "10.0.1.123:9800"]
}
}
----
Expand Down