Create xpack.monitoring.elasticsearch.collection.enabled setting #33290
Description
Currently, Elasticsearch collects its own monitoring metrics and ships them to the monitoring cluster (which may be local or remote). The longer-term plan for Elastic stack monitoring is for Metricbeat to run along side Elasticsearch, collect monitoring data by calling Elasticsearch APIs and ship this data to the monitoring cluster.
As a prerequisite to asking users to setup Metricbeat for monitoring Elasticsearch, we need to ask them to turn off Elasticsearch's own internal collection. Otherwise duplicate documents for Elasticsearch monitoring will show up in the monitoring cluster.
This can be done by exposing a new cluster setting, xpack.monitoring.elasticsearch.collection.enabled, which will default to true for BWC.
Two notes on naming this setting:
- Kibana has a similar setting named
xpack.monitoring.kibana.collection.enabled, which does exactly the same thing as is described here, but for Kibana xpack.monitoring.collection.enabledis already taken in Elasticsearch and does more than what is described in this issue.