35 lines
1.3 KiB
Plaintext
35 lines
1.3 KiB
Plaintext
|
[role="xpack"]
|
||
|
|
[[pause-export]]
|
||
|
|
== Pausing Data Collection
|
||
|
|
|
||
|
|
To stop generating {monitoring} data in {es}, disable data collection:
|
||
|
|
|
||
|
|
[source,yaml]
|
||
|
|
---------------------------------------------------
|
||
|
|
xpack.monitoring.collection.enabled: false
|
||
|
|
---------------------------------------------------
|
||
|
|
|
||
|
|
When this setting is `false`, {es} monitoring data is not collected and all
|
||
|
|
monitoring data from other sources such as {kib}, Beats, and Logstash is ignored.
|
||
|
|
|
||
|
|
You can update this setting by using the
|
||
|
|
{ref}/cluster-update-settings.html[Cluster Update Settings API].
|
||
|
|
|
||
|
|
If you want to separately disable a specific exporter, you can specify the
|
||
|
|
`enabled` setting (which defaults to `true`) per exporter. For example:
|
||
|
|
|
||
|
|
[source,yaml]
|
||
|
|
---------------------------------------------------
|
||
|
|
xpack.monitoring.exporters.my_http_exporter:
|
||
|
|
type: http
|
||
|
|
host: ["10.1.2.3:9200", "10.1.2.4:9200"]
|
||
|
|
enabled: false <1>
|
||
|
|
---------------------------------------------------
|
||
|
|
<1> 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.
|