Monitoring is enabled by default when you install X-Pack. You configure
elasticsearch.yml to control how data is collected from your
To adjust how monitoring data is displayed in the Monitoring UI, you configure
xpack.monitoring settings in
kibana.yml. To control how monitoring data is collected from
Logstash, you configure
xpack.monitoring settings in
For more information, see Monitoring the Elastic Stack.
falseto disable Elasticsearch X-Pack monitoring for Elasticsearch.
Sets the timeout for collecting the cluster state. Defaults to
Sets the timeout for collecting the cluster statistics. Defaults to
Controls which indices Monitoring collects data from. Defaults to all indices. Specify the index names as a comma-separated list, for example
test1,test2,test3. Names can include wildcards, for example
test*. You can explicitly include or exclude indices by prepending
+to include the index, or
-to exclude the index. For example, to include all indices that start with
test3, you could specify
You can update this setting through the Cluster Update Settings API.
Sets the timeout for collecting index statistics. Defaults to
Sets the timeout for collecting total indices statistics. Defaults to
- Configures where the agent stores monitoring data. By default, the agent uses a local exporter that indexes monitoring data on the cluster where it is installed. Use an HTTP exporter to send data to a separate monitoring cluster. For more information, see Setting up a Separate Monitoring Cluster.
Controls whether or not all recoveries are collected. Set to
trueto collect only active recoveries. Defaults to
Sets the timeout for collecting the recovery information. Defaults to
Controls how often data samples are collected. Defaults to
10s. If you modify the collection interval, set the
kibana.ymlto the same value. Set to
-1to temporarily disable data collection. You can update this setting through the Cluster Update Settings API.
Sets the retention duration beyond which the indices created by a Monitoring exporter will be automatically deleted. Defaults to
This setting has a minimum value of
1d(1 day) to ensure that something is being monitored, and it cannot be disabled.
This setting currently only impacts
local-type exporters. Indices created using the
httpexporter will not be deleted automatically.
You can configure the following TLS/SSL settings. If the settings are not configured, the Default TLS/SSL Settings are used.
Supported protocols with versions. Valid protocols:
TLSv1.2. Defaults to
TLSv1. Defaults to the value of
Controls the verification of certificates. Valid values are
full. Defaults to the value of
Supported cipher suites can be found in Oracle’s
Java Cryptography Architecture documentation. Defaults to the value of
The following settings are used to specify a private key, certificate, and the trusted certificates that should be used when communicating over an SSL/TLS connection. If none of the settings below are specified, the Default TLS/SSL Settings are used. A private key and certificate are optional and would be used if the server requires client authentication for PKI authentication. If none of the settings below are specified, the Default TLS/SSL Settings are used.
When using PEM encoded files, use the following settings:
- Path to a PEM encoded file containing the private key.
- The passphrase that will be used to decrypt the private key. This value is optional as the key may not be encrypted.
- Path to a PEM encoded file containing the certificate (or certificate chain) that will be presented when requested.
- List of paths to the PEM encoded certificate files that should be trusted.
When using Java keystore files (JKS), which contain the private key, certificate and certificates that should be trusted, use the following settings:
- Path to the keystore that holds the private key and certificate.
- Password to the keystore.
Password for the private key in the keystore. Defaults to the
same value as
- Path to the truststore file.
- Password to the truststore.