This section summarizes the changes in each release. For information about upgrading Marvel, see Upgrading Marvel.
You must run the version of Marvel that matches the version of Elasticsearch you are running. For example, Marvel 2.1.2 requires Elasticsearch 2.1.2. Marvel 2.1.x is compatible with Kibana 4.3.x.
February 2, 2016
- Adds support for Elasticssearch 2.1.2
December 17, 2015
- 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.
November 24, 2015
- 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.
- 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_statsAPI to determine which Marvel indices are needed to generate the stats.
November 24, 2015
- Adds support for Elasticsearch 2.0.1.
October 28, 2015
Breaking Changes. Marvel 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
marvel.enabledconfiguration parameter to
marvel.agent.enabledparameter 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.
- 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