[DOCS] Clarify BWC of monitoring clusters (#63151)

This commit is contained in:
Lisa Cawley 2020-10-02 14:06:20 -07:00 committed by lcawl
parent 4de6104dae
commit 69c56d55dc
1 changed files with 5 additions and 3 deletions

View File

@ -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 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}, not. For example, you can use {metricbeat} to ship monitoring data about {kib},
{es}, {ls}, and Beats to the monitoring cluster. {es}, {ls}, and Beats to the monitoring cluster.
If you are sending your data to the {esms-init}, see <<esms>>.
[IMPORTANT] [IMPORTANT]
========================= =========================
@ -32,8 +31,11 @@ For example, you might set up a two host cluster with the nodes `es-mon-1` and
-- --
[IMPORTANT] [IMPORTANT]
=============================== ===============================
* To monitor an {es} {major-version} cluster, you must run {es} {major-version} * Ideally the monitoring cluster and the production cluster run on the same
on the monitoring cluster. {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 <<ingest,ingest node>> in the monitoring * There must be at least one <<ingest,ingest node>> in the monitoring
cluster; it does not need to be a dedicated ingest node. cluster; it does not need to be a dedicated ingest node.
=============================== ===============================