github-mirrors/logstash
1
0
Fork 0
mirror of https://github.com/elastic/logstash.git synced 2025-04-24 14:47:19 -04:00
Code Issues Projects Releases Packages Wiki Activity

Clarify monitoring hosts should not be master-only

Browse source 
This commit clarifies that Logstash monitoring metrics should not be
routed through master-only nodes, and should instead prefer coordinating
nodes.

Fixes #11194
This commit is contained in:
Jason Tedor 2019-09-16 11:53:53 -07:00 • committed by Ry Biesemeyer
parent 9c9266fe3a
commit 0d6bb46edc
1 changed files with 6 additions and 0 deletions
Download patch file Download diff file Expand all files Collapse all files

6
docs/static/settings/monitoring-settings.asciidoc vendored
View file

@ -28,6 +28,12 @@ Logstash metrics must be routed through your production cluster. You can specify
a single host as a string, or specify multiple hosts as an array. Defaults to a single host as a string, or specify multiple hosts as an array. Defaults to
`http://localhost:9200`. `http://localhost:9200`.
NOTE: If your Elasticsearch cluster is configured with dedicated master-eliglble
nodes, Logstash metrics should _not_ be routed to these nodes, as doing so can
create resource contention and impact the stability of the Elasticsearch
cluster. Therefore, do not include such nodes in
`xpack.monitoring.elasticsearch.hosts`.
`xpack.monitoring.elasticsearch.username` and `xpack.monitoring.elasticsearch.password`:: `xpack.monitoring.elasticsearch.username` and `xpack.monitoring.elasticsearch.password`::
If your {es} is protected with basic authentication, these settings provide the If your {es} is protected with basic authentication, these settings provide the