Installing Swarm Metrics, ES 2.3.3

For description of Swarm Metrics, its components, templates, and the set of rolling indices it generates, see Swarm Historical Metrics.

Index defaults

For ES 2.3.3, indices are configured with 3 shards and one additional replica per index. If more shards or replicas are desired, contact DataCore Support for help with that configuration.

Once the current version of Elasticsearch is running, install Swarm Metrics on one of the Elasticsearch servers or another system running RHEL/CentOS 6.

  1. Install the new ES curator package. (See Elasticsearch for details.)

    1. Download and install the public signing key for Elasticsearch.

      rpm --import https://packages.elastic.co/GPG-KEY-elasticsearch
    2. Create a yum repository entry. In /etc/yum.repos.d, create the file, "curator.repo" and include the section correct for this version of RHEL/CentOS:

      [curator-4] name=CentOS/RHEL 6 repository for Elasticsearch Curator 4.x packages baseurl=http://packages.elastic.co/curator/4/centos/6 gpgcheck=1 gpgkey=http://packages.elastic.co/GPG-KEY-elasticsearch enabled=1
    3. Install the ES curator package.

      yum install elasticsearch-curator
  2. In the Swarm bundle, locate the Metrics RPM: caringo-elasticsearch-metrics-<version>.noarch.rpm

  3. Install the metrics package. 

  4. Update the configuration file for the metrics curator: /etc/caringo-elasticsearch-metrics/metrics.cfg

  5. Configure the metrics settings for the Swarm Storage cluster. 
    Using either the Swarm UI or SNMP, update these settings. (See Persisted Settings (SNMP) for how to update settings using SNMP.) Note: the dynamic (SNMP-enabled) values in the config file affect a new cluster on first deployment.

  6. To start collecting metrics, manually run curator to prime the indexing setup, which defines the metrics schemas, creates empty indices with those schemas, and sets up aliases to the indices. The curator runs at midnight by default. For a new installation it runs at the top of the next hour. Running the curator guarantees the current day's indices exist and all aliases are up to date, so metrics can begin to be collected (priming does not generate any metrics data). 

    Use this command to run curator manually:

  7. After metrics are configured in the Swarm cluster, the first metrics data appears within the number of seconds of metrics.period, which defaults to 15 minutes. Look for "create_mapping [metrics]" log events in the Elasticsearch log (by default: /var/log/elasticsearch/[ES-cluster-name].log.

    See Swarm Metrics Troubleshooting if needed. 

  8. Return to Migrating from Older Elasticsearch, or else resume the Elasticsearch installationInstalling Elasticsearch

© DataCore Software Corporation. · https://www.datacore.com · All rights reserved.