From 69c56d55dc0301a62b672d7f1328f1fb8ec2c206 Mon Sep 17 00:00:00 2001 From: Lisa Cawley Date: Fri, 2 Oct 2020 14:06:20 -0700 Subject: [PATCH] [DOCS] Clarify BWC of monitoring clusters (#63151) --- docs/reference/monitoring/production.asciidoc | 8 +++++--- 1 file changed, 5 insertions(+), 3 deletions(-) diff --git a/docs/reference/monitoring/production.asciidoc b/docs/reference/monitoring/production.asciidoc index a05003b65d9..44c14dd7c0f 100644 --- a/docs/reference/monitoring/production.asciidoc +++ b/docs/reference/monitoring/production.asciidoc @@ -6,7 +6,6 @@ In production, you should send monitoring data to a separate _monitoring cluster so that historical data is available even when the nodes you are monitoring are not. For example, you can use {metricbeat} to ship monitoring data about {kib}, {es}, {ls}, and Beats to the monitoring cluster. -If you are sending your data to the {esms-init}, see <>. [IMPORTANT] ========================= @@ -32,8 +31,11 @@ For example, you might set up a two host cluster with the nodes `es-mon-1` and -- [IMPORTANT] =============================== -* To monitor an {es} {major-version} cluster, you must run {es} {major-version} -on the monitoring cluster. +* Ideally the monitoring cluster and the production cluster run on the same +{stack} version. However, a monitoring cluster on the latest release of +{major-version} also works with production clusters that use the same major +version. Monitoring clusters that use {major-version} also work with production +clusters that use the latest release of {prev-major-version}. * There must be at least one <> in the monitoring cluster; it does not need to be a dedicated ingest node. ===============================