WARNING: Version 5.2 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.
Migrating from Marveledit
Prior to 5.0, monitoring functionality was provided as a separate Marvel plugin for Elasticsearch and Kibana. As of 5.0, all of Marvel’s features have been rolled into X-Pack monitoring.
To migrate to X-Pack monitoring, you simply need to install X-Pack and update your monitoring settings:
| Monitoring 2.x Settings | X-Pack 5.0 Settings |
|---|---|
|
|
|
|
|
|
For example marvel.history.duration is now xpack.monitoring.history.duration,
and marvel.agent.interval is now xpack.monitoring.collection.interval.
See X-Pack Settings for the complete list of X-Pack monitoring settings and other X-Pack configuration options.
All of the Marvel metric indexes created by Marvel 2.3+ (named like
.marvel-es-1-*) will be automatically aliased to be used by Monitoring.
Marvel metric indexes created by 2.0 through 2.2 are not compatible with
Monitoring so they are unused and unmodified. You can delete them by running:
DELETE /.marvel-es-20*
Marvel’s data index (named like .marvel-es-data or .marvel-es-data-1) is
also unused and unmodified. Monitoring will recreate a new data index soon
after startup so there is no real need to keep Marvel’s data indexes. You can
delete them by running:
DELETE /.marvel-es-data*
Using an External Monitoring Clusteredit
To use an external monitoring cluster to monitor an Elasticsearch 5.0 cluster, you must run Elasticsearch 5.0 on the monitoring cluster. For more information about external monitoring clusters, see Setting up a Separate Monitoring Cluster.