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

Add experimental tags for internal collection

Browse source 
Fixes #11823
This commit is contained in:
Karen Metts 2020-04-20 16:38:28 -04:00
parent beec172e22
commit cf890d0df7
4 changed files with 7 additions and 27 deletions
Download patch file Download diff file Expand all files Collapse all files

19
docs/static/monitoring/monitoring-internal-legacy.asciidoc vendored
View file

@ -5,25 +5,6 @@
<titleabbrev>Legacy internal collection</titleabbrev>
++++
IMPORTANT: Use <<monitoring-internal-collection,internal collection>> or
<<monitoring-with-metricbeat, {metricbeat} collection>> instead of legacy
internal collection. If you are currently using legacy internal collection, you
should migrate to either Metricbeat collection or internal collection.
==== Migrating from legacy internal collection to new internal collection
Migrating from legacy internal collection to new
<<monitoring-internal-collection,Internal collection>> is straightforward.
** Drop the `xpack.` prefix from your configuration settings.
For example, `xpack.monitoring.enabled` is now `monitoring.enabled`. See
<<monitoring-settings, Monitoring Settings>> for the full list.
** Change the hosts settings and configuration options to point to the monitoring
cluster instead of the production cluster.
** If you don’t have an Elasticsearch output plugin configured in the pipelines,
add the <<monitoring-cluster-uuid,`monitoring.cluster_uuid`>> setting to your
logstash.yml.
==== Components for legacy internal collection
Monitoring {ls} with legacy internal collection uses these components:

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

@ -1,14 +1,12 @@
[role="xpack"]
[[monitoring-internal-collection]]
=== Use internal collectors to send monitoring data
=== Use internal collectors to send monitoring data (Experimental)
experimental[]
++++
<titleabbrev>Internal collection</titleabbrev>
<titleabbrev>Internal collection (Experimental)</titleabbrev>
++++
Internal collectors send {ls} monitoring data directly to your _monitoring_ cluster.
The benefit of internal collection is that you have fewer pieces of software to
install and maintain.
<<monitoring-with-metricbeat, {metricbeat} collection>> is available as an alternative.
IMPORTANT: All Logstash nodes must share the same setup.
@ -16,6 +14,7 @@ Otherwise, monitoring data might be routed in different ways or to different pla
[[configure-internal-collectors]]
==== Configure {ls} monitoring with internal collectors
experimental[]
++++
<titleabbrev>Configure internal collection</titleabbrev>
++++

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

@ -21,9 +21,8 @@ monitoring data from your {ls} instance and sends it directly to your monitoring
cluster. The benefit of Metricbeat collection is that the monitoring
agent remains active even if the {ls} instance does not.
* <<monitoring-internal-collection,Internal collection>>. Internal collectors send
monitoring data directly to your monitoring cluster. The benefit of internal
collection is that you have fewer pieces of software to install and maintain.
* <<monitoring-internal-collection,Internal collection (Experimental)>>.
Internal collectors send monitoring data directly to your monitoring cluster.
* <<monitoring-internal-collection-legacy,Legacy internal collection>>. Legacy
internal collectors send monitoring data to your production cluster.

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

@ -1,6 +1,7 @@
[role="xpack"]
[[monitoring-settings]]
==== Monitoring settings for internal collection
experimental[]
++++
<titleabbrev>Monitoring Settings</titleabbrev>
++++