Skip to content

Commit 4103d3b

Browse files
authored
[DOCS] Adds monitoring requirement for ingest node (elastic#36665)
1 parent eb59c1f commit 4103d3b

File tree

2 files changed

+9
-3
lines changed

2 files changed

+9
-3
lines changed

docs/reference/monitoring/collecting-monitoring-data.asciidoc

+5-3
Original file line numberDiff line numberDiff line change
@@ -101,11 +101,13 @@ the `xpack.monitoring.collection.interval` setting 10 seconds. See
101101
+
102102
--
103103
By default, the data is stored on the same cluster by using a
104-
<<local-exporter,`local` exporter>>.
105-
106-
Alternatively, you can use an <<http-exporter,`http` exporter>> to send data to
104+
<<local-exporter,`local` exporter>>. Alternatively, you can use an <<http-exporter,`http` exporter>> to send data to
107105
a separate _monitoring cluster_.
108106

107+
IMPORTANT: The {es} {monitor-features} use ingest pipelines, therefore the
108+
cluster that stores the monitoring data must have at least one
109+
<<ingest,ingest node>>.
110+
109111
For more information about typical monitoring architectures,
110112
see {stack-ov}/how-monitoring-works.html[How Monitoring Works].
111113
--

docs/reference/monitoring/configuring-metricbeat.asciidoc

+4
Original file line numberDiff line numberDiff line change
@@ -164,6 +164,10 @@ output.elasticsearch:
164164
<1> In this example, the data is stored on a monitoring cluster with nodes
165165
`es-mon-1` and `es-mon-2`.
166166

167+
IMPORTANT: The {es} {monitor-features} use ingest pipelines, therefore the
168+
cluster that stores the monitoring data must have at least one
169+
<<ingest,ingest node>>.
170+
167171
For more information about these configuration options, see
168172
{metricbeat-ref}/elasticsearch-output.html[Configure the {es} output].
169173
--

0 commit comments

Comments
 (0)