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

elastic · May 15, 2020 · 4b8eb06 · 4b8eb06
1 parent cdb59c7
commit 4b8eb06
Show file tree

Hide file tree

Showing 2 changed files with 6 additions and 6 deletions.
diff --git a/docs/user/monitoring/configuring-monitoring.asciidoc b/docs/user/monitoring/configuring-monitoring.asciidoc
@@ -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[]
diff --git a/docs/user/monitoring/monitoring-kibana.asciidoc b/docs/user/monitoring/monitoring-kibana.asciidoc
@@ -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