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

Incorporate review comments

Browse source 
Fixes #11789
This commit is contained in:
Karen Metts 2020-04-16 15:08:25 -04:00
parent b67ffceb53
commit 7b68aee7f3
2 changed files with 10 additions and 13 deletions
Download patch file Download diff file Expand all files Collapse all files

7
docs/static/monitoring/monitoring-internal.asciidoc vendored
View file

@ -11,6 +11,9 @@ install and maintain.
<<monitoring-with-metricbeat, {metricbeat} collection>> is available as an alternative.
IMPORTANT: All Logstash nodes must share the same setup.
Otherwise, monitoring data might be routed in different ways or to different places.
[[configure-internal-collectors]]
==== Configure {ls} monitoring with internal collectors
++++
@ -23,7 +26,7 @@ To monitor Logstash nodes:
monitoring architectures, see {ref}/how-monitoring-works.html[How monitoring
works] in the {ref}[Elasticsearch Reference].
. Verify that the `monitoring.collection.enabled` setting is `true` on the
. Verify that the `xpack.monitoring.collection.enabled` setting is `true` on the
monitoring cluster. If that setting is `false`, the collection of monitoring data
is disabled in {es}, and data is ignored from all other sources.
@ -36,7 +39,7 @@ information about these settings, see <<monitoring-settings>>.
--
[source,yaml]
--------------------------------------------------
monitoring.elasticsearch.hosts: ["http://es-prod-node-1:9200", "http://es-prod-node-2:9200"]
monitoring.elasticsearch.hosts: ["http://es-monitoring-node-1:9200", "http://es-monitoring-node-2:9200"]
monitoring.elasticsearch.username: "logstash_system"
monitoring.elasticsearch.password: "changeme"
--------------------------------------------------

16
docs/static/monitoring/monitoring-output.asciidoc vendored
View file

@ -28,23 +28,17 @@ the following default configuration is used:
monitoring.elasticsearch.hosts: [ "http://localhost:9200" ]
---------------------------------------------------
//TODO: Verify the following sentence:
All data produced by Logstash monitoring is indexed in the monitoring
cluster by using the `.monitoring-logstash` template, which is managed by the
{ref}/es-monitoring-exporters.html[exporters] within {es}.
cluster using the `.monitoring-logstash` template.
If you are working with a cluster that has {security-features} enabled, extra
steps are necessary to properly configure Logstash. For more information, see
<<configuring-logstash>>.
//TODO: Verify the following sentence:
IMPORTANT: When discussing security relative to the `elasticsearch` output,
remember that all users are managed on the production cluster, which is
identified in the `monitoring.elasticsearch.hosts` setting. This is particularly
important when you move from development environments to production
IMPORTANT: When discussing security relative to the `monitoring.elasticsearch`
settings, remember that all users are managed on the monitoring cluster, which
is identified in the `monitoring.elasticsearch.hosts` setting. This is
particularly important when you move from development environments to production
environments, where you often have dedicated monitoring clusters.
For more information about the configuration options for the output, see