From 33cac52b2c1919048e5e0772f1cb8911e88a456c Mon Sep 17 00:00:00 2001
From: Lisa Cawley <lcawley@elastic.co>
Date: Thu, 24 Jan 2019 09:14:08 -0800
Subject: [PATCH] [DOCS] Remove beta tag from metricbeat monitoring (#37791)

---
 docs/reference/monitoring/configuring-metricbeat.asciidoc | 2 --
 docs/reference/monitoring/index.asciidoc                  | 2 +-
 2 files changed, 1 insertion(+), 3 deletions(-)

diff --git a/docs/reference/monitoring/configuring-metricbeat.asciidoc b/docs/reference/monitoring/configuring-metricbeat.asciidoc
index dd7811b3421..a161559d3f1 100644
--- a/docs/reference/monitoring/configuring-metricbeat.asciidoc
+++ b/docs/reference/monitoring/configuring-metricbeat.asciidoc
@@ -6,8 +6,6 @@
 <titleabbrev>Collecting monitoring data with {metricbeat}</titleabbrev>
 ++++
 
-beta[]
-
 In 6.5 and later, you can use {metricbeat} to collect data about {es} 
 and ship it to the monitoring cluster, rather than routing it through exporters 
 as described in <<collecting-monitoring-data>>. 
diff --git a/docs/reference/monitoring/index.asciidoc b/docs/reference/monitoring/index.asciidoc
index 13e7314f8af..fbda72e0f97 100644
--- a/docs/reference/monitoring/index.asciidoc
+++ b/docs/reference/monitoring/index.asciidoc
@@ -33,7 +33,7 @@ indexing (storage). The routing and indexing processes in {es} are handled by
 what are called <<es-monitoring-collectors,collectors>> and 
 <<es-monitoring-exporters,exporters>>. 
 
-beta[] Alternatively, in 6.4 and later, you can use {metricbeat} to collect 
+Alternatively, in 6.4 and later, you can use {metricbeat} to collect 
 monitoring data about {kib} and ship it directly to the monitoring cluster, 
 rather than routing it through the production cluster. In 6.5 and later, you 
 can also use {metricbeat} to collect and ship data about {es}.