Pausing data collection

Warning

The Elasticsearch Monitoring plugin is deprecated and will be removed in 10.0. Choose one of the following replacements to monitor your Elasticsearch cluster:

AutoOps (recommended): Simplifies cluster management through performance recommendations, resource utilization visibility, and real-time issue detection with resolution paths.
Stack monitoring with Elastic Agent or Metricbeat: Collect logs and metrics from Elasticsearch and ship them to a monitoring cluster for visualization in Kibana.

To help you decide, refer to the AutoOps and Stack Monitoring comparison.

To stop generating monitoring data in Elasticsearch, disable data collection:

xpack.monitoring.collection.enabled: false

When this setting is false, Elasticsearch monitoring data is not collected and all monitoring data from other sources such as Kibana, Beats, and Logstash is ignored.

You can update this setting by using the Cluster Update Settings API.

If you want to collect data from sources such as Kibana, Beats, and Logstash but not collect data about your Elasticsearch cluster, you can disable data collection just for Elasticsearch:

xpack.monitoring.collection.enabled: true
xpack.monitoring.elasticsearch.collection.enabled: false

If you want to separately disable a specific exporter, you can specify the enabled setting (which defaults to true) per exporter. For example:

xpack.monitoring.exporters.my_http_exporter:
  type: http
  host: ["10.1.2.3:9200", "10.1.2.4:9200"]
  enabled: false

Disable the named exporter. If the same name as an existing exporter is not used, then this will create a completely new exporter that is completely ignored. This value can be set dynamically by using cluster settings.

Note

Defining a disabled exporter prevents the default exporter from being created.

To re-start data collection, re-enable these settings.