honeymoose
/
OpenSearch
mirror of https://github.com/honeymoose/OpenSearch.git
1
0
Fork 0
Code Issues Packages Projects Releases Wiki Activity

[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
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

8
docs/reference/monitoring/production.asciidoc
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
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 <<esms>>.
[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 <<ingest,ingest node>> in the monitoring
cluster; it does not need to be a dedicated ingest node.
===============================