From version 5.0 onward, Marvel is part of X-Pack. For more information, see
Monitoring the Elastic Stack.
Release Notes
editRelease Notes
editThis section summarizes the changes in each release. For information about upgrading Marvel, see Upgrading Marvel.
Version Compatibility
editYou must run the version of Marvel that matches the version of Elasticsearch you are running. For example, Marvel 2.2.1 requires Elasticsearch 2.2.1. Marvel 2.1.x is compatible with Kibana 4.3.x.
Change List
edit2.2.1
editMarch 15, 2016
Bug Fixes
- Fix a bug when Marvel is configured to export data over HTTP on a monitoring cluster protected by Shield (with SSL).
2.2.0
editFebruary 2, 2016
Enhancements
- Enable access to the License page from the cluster status bar.
- Allow configuration of a monthly interval for Marvel indices instead of limiting it to daily.
- Provide a sha1 hash for the Marvel app download.
Bug Fixes
- Minor UI improvements.
2.1.2
editFebruary 2, 2016
Enhancements
- Adds support for Elasticssearch 2.1.2
2.1.1
editDecember 17, 2015
Bug Fixes
- Check the Kibana version to ensure compatibility.
- Respect opt-out for statistics reporting in all cases.
- Fixed transport address not showing on the node detail page.
- Fixed the table filtering on the node listing page.
2.1.0
editNovember 24, 2015
Enhancements
- Display a node type indicator on the Node Listing and Node Detail pages.
- Show the online/offline status of nodes.
- Remove the Time Picker from the Cluster Listing page.
Bug Fixes
- Multiple fixes for showing historical data.
- Filter out derivative calculations where the start and end times are incomplete time buckets.
- Cluster table sorting.
-
Use the new Elasticsearch
_field_stats
API to determine which Marvel indices are needed to generate the stats.
2.0.1
editNovember 24, 2015
Enhancements
- Adds support for Elasticsearch 2.0.1.
2.0.0
editOctober 28, 2015
Breaking ChangesMarvel 2.0.0 is a complete rewrite from Marvel 1.3. If you are upgrading from Marvel 1.3:
- Note that the Marvel agent plugin only needs to be installed on the Elasticsearch nodes you are monitoring.
-
If you need to stop collecting data from a node, remove the plugin or set
the
marvel.enabled
configuration parameter tofalse
. Themarvel.agent.enabled
parameter is no longer supported. - The Marvel exporter settings have changed. If you are using a separate monitoring cluster, you will need to update your configuration. For more information, see Setting up a Separate Monitoring Cluster.
New Features
- Fully-integrated with Kibana 4.2 as a Kibana plugin.
- Supports Multiple clusters for Paid Subscriptions
- Reduced data footprint for Marvel indices
- Simplified dashboards for Indices and Nodes
- Better support for large clusters