mirror of
https://github.com/elastic/logstash.git
synced 2025-04-24 22:57:16 -04:00
parent
5587c9d7ac
commit
17c11508da
3 changed files with 3 additions and 5 deletions
|
@ -2,11 +2,9 @@
|
|||
[[monitoring-internal-collection]]
|
||||
=== Collect {ls} monitoring data using internal collectors
|
||||
++++
|
||||
<titleabbrev>Internal collection (deprecated)</titleabbrev>
|
||||
<titleabbrev>Internal collection</titleabbrev>
|
||||
++++
|
||||
|
||||
deprecated[7.7.0]
|
||||
|
||||
Using internal collectors for {ls} {monitoring} these components:
|
||||
|
||||
* <<logstash-monitoring-collectors,Collectors>>
|
||||
|
|
|
@ -6,7 +6,7 @@
|
|||
<titleabbrev>{metricbeat} collection</titleabbrev>
|
||||
++++
|
||||
|
||||
In 7.3 and later, you can use {metricbeat} to collect data about {ls}
|
||||
You can use {metricbeat} to collect data about {ls}
|
||||
and ship it to the monitoring cluster, rather than routing it through the
|
||||
production cluster as described in <<monitoring-internal-collection>>.
|
||||
|
||||
|
|
|
@ -17,7 +17,7 @@ Make sure monitoring is enabled on your {es} cluster. Then configure *one* of
|
|||
these methods to collect {ls} metrics:
|
||||
|
||||
* <<monitoring-with-metricbeat, {metricbeat} collection>>
|
||||
* <<monitoring-internal-collection,Internal collection (deprecated)>>
|
||||
* <<monitoring-internal-collection,Internal collection>>
|
||||
|
||||
|
||||
include::monitoring-mb.asciidoc[]
|
||||
|
|
Loading…
Add table
Add a link
Reference in a new issue