github-mirrors/logstash
1
0
Fork 0
mirror of https://github.com/elastic/logstash.git synced 2025-04-25 07:07:54 -04:00
Code Issues Projects Releases Packages Wiki Activity

Doc updates for internal collectors

Browse source 
Fixes #11789
This commit is contained in:
Karen Metts 2020-04-14 16:39:27 -04:00
parent ee2d819d44
commit b67ffceb53
2 changed files with 6 additions and 5 deletions
Download patch file Download diff file Expand all files Collapse all files

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

@ -96,8 +96,6 @@ host, and select **Monitoring** from the side navigation. Metrics reported from
your Logstash nodes should be visible in the Logstash section. When security is your Logstash nodes should be visible in the Logstash section. When security is
enabled, you must log in to {kib} as a user who has the `kibana_user` and enabled, you must log in to {kib} as a user who has the `kibana_user` and
`monitoring_user` roles. `monitoring_user` roles.
+
image::images/monitoring-ui.png["Monitoring",link="monitoring/images/monitoring-ui.png"]
include::../settings/monitoring-settings.asciidoc[] include::../settings/monitoring-settings.asciidoc[]
@ -112,9 +110,7 @@ Monitoring {ls} with internal collectors uses these components:
These pieces live outside of the default Logstash pipeline in a dedicated These pieces live outside of the default Logstash pipeline in a dedicated
monitoring pipeline. This configuration ensures that all data and processing has monitoring pipeline. This configuration ensures that all data and processing has
a minimal impact on ordinary Logstash processing. Existing Logstash features, a minimal impact on ordinary Logstash processing.
such as the <<plugins-outputs-elasticsearch,`elasticsearch` output>>, can be
reused to benefit from its retry policies.
NOTE: The `elasticsearch` output for Logstash monitoring is configured NOTE: The `elasticsearch` output for Logstash monitoring is configured
exclusively through settings in `logstash.yml`. exclusively through settings in `logstash.yml`.

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

@ -28,6 +28,8 @@ the following default configuration is used:
monitoring.elasticsearch.hosts: [ "http://localhost:9200" ] monitoring.elasticsearch.hosts: [ "http://localhost:9200" ]
--------------------------------------------------- ---------------------------------------------------
//TODO: Verify the following sentence:
All data produced by Logstash monitoring is indexed in the monitoring All data produced by Logstash monitoring is indexed in the monitoring
cluster by using the `.monitoring-logstash` template, which is managed by the cluster by using the `.monitoring-logstash` template, which is managed by the
{ref}/es-monitoring-exporters.html[exporters] within {es}. {ref}/es-monitoring-exporters.html[exporters] within {es}.
@ -36,6 +38,9 @@ If you are working with a cluster that has {security-features} enabled, extra
steps are necessary to properly configure Logstash. For more information, see steps are necessary to properly configure Logstash. For more information, see
<<configuring-logstash>>. <<configuring-logstash>>.
//TODO: Verify the following sentence:
IMPORTANT: When discussing security relative to the `elasticsearch` output, IMPORTANT: When discussing security relative to the `elasticsearch` output,
remember that all users are managed on the production cluster, which is remember that all users are managed on the production cluster, which is
identified in the `monitoring.elasticsearch.hosts` setting. This is particularly identified in the `monitoring.elasticsearch.hosts` setting. This is particularly