Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

[DOCS] Rename monitoring collection from internal to legacy #65781

Merged
merged 1 commit into from
May 15, 2020
Merged

[DOCS] Rename monitoring collection from internal to legacy #65781

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
6 changes: 3 additions & 3 deletions docs/user/monitoring/configuring-monitoring.asciidoc
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -8,15 +8,15 @@
If you enable the {monitor-features} in your cluster, there are two methods to
collect metrics about {kib}:

* <<monitoring-kibana>>
* <<monitoring-metricbeat>>
* <<monitoring-metricbeat,{metricbeat} collection methods>>
* <<monitoring-kibana,Legacy collection methods>>

You can also use {kib} to
<<monitoring-data,visualize monitoring data from across the {stack}>>.

To learn about monitoring in general, see
{ref}/monitor-elasticsearch-cluster.html[Monitor a cluster].

include::monitoring-kibana.asciidoc[]
include::monitoring-metricbeat.asciidoc[]
include::viewing-metrics.asciidoc[]
include::monitoring-kibana.asciidoc[]
6 changes: 3 additions & 3 deletions docs/user/monitoring/monitoring-kibana.asciidoc
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -1,15 +1,15 @@
[role="xpack"]
[[monitoring-kibana]]
=== Collecting {kib} monitoring data
=== Collecting monitoring data using legacy collectors
++++
<titleabbrev>Collecting monitoring data</titleabbrev>
<titleabbrev>Legacy collection methods</titleabbrev>
++++

If you enable the Elastic {monitor-features} in your cluster, you can
optionally collect metrics about {kib}.

The following method involves sending the metrics to the production cluster,
which ultimately routes them to the monitoring cluster. For an alternative
which ultimately routes them to the monitoring cluster. For the recommended
method, see <<monitoring-metricbeat>>.

To learn about monitoring in general, see
Expand Down