WARNING: Version 5.6 of the Elastic Stack has passed its EOL date.

This documentation is no longer being maintained and may be removed. If you are running this version, we strongly advise you to upgrade. For the latest information, see the current release documentation.

« Monitoring Kibana Alerting on Cluster and Index Events »
Elastic Docs ›X-Pack for the Elastic Stack [5.6] ›Monitoring the Elastic Stack

Configuring Monitoring

edit
IMPORTANT: This documentation is no longer updated. Refer to Elastic's version policy and the latest documentation.

Configuring Monitoring

edit

Advanced monitoring settings enable you to control how frequently data is collected, configure timeouts, and set the retention period for locally-stored monitoring indices. You can also adjust how monitoring data is displayed. For more information, see Monitoring Settings.

Configuring Monitoring’s Indices

edit

Index templates are used to configure the indices that store the monitoring data collected from a cluster.

You can retrieve the templates through the _template API:

GET /_template/.monitoring-*

By default, the template configures one shard and one replica for the monitoring indices. To override the default settings, add your own template:

  1. Set the template pattern to .monitoring-*.
  2. Set the template order to 1. This ensures your template is applied after the default template, which has an order of 0.
  3. Specify the number_of_shards and/or number_of_replicas in the settings section.

For example, the following template increases the number of shards to five and the number of replicas to two.

PUT /_template/custom_monitoring
{
    "template": ".monitoring-*",
    "order": 1,
    "settings": {
        "number_of_shards": 5,
        "number_of_replicas": 2
    }
}

Only set the number_of_shards and number_of_replicas in the settings section. Overriding other monitoring template settings could cause your monitoring dashboards to stop working correctly.

« Monitoring Kibana Alerting on Cluster and Index Events »