Monitoring Components - EEP 7.0.0 Release Notes
The notes below relate specifically to the HPE Ezmeral Data Fabric.
These release notes contain only data-fabric-specific information and are not necessarily cumulative in nature. For information about how to use the release notes, see Ecosystem Component Release Notes.
Version | The EEP 7.0.0 release contains the
following monitoring-component versions:
|
Release Date | September 2020 |
Version Interoperability | Component Versions for Released EEPs |
Package Names | Package Names for Ecosystem Packs (EEPs) |
New in This Release
- EEP 7.0.0 includes updates to Collectd, Fluentd, Opentsdb, Elasticsearch, Grafana, and Kibana. To compare Monitoring component versions, see MEP Components and OS Support.
Fixes
Principal fixes in this release include:
- ES-20: Elastic Search Key management seems unnecessarily complex. For more information, see "Simplified Installation for Log Monitoring" in Installation Notes (Release 7.1.0).
- COLD-168: Collectd process leak memory.
- GRAF-57: Grafana: SSRF Incorrect access control vulnerability (CVE-2020-13379).
Known Issues and Limitations
This release contains the following known issues and limitations:
- COLD-162: Graphs in the Control System do not
display metrics for file system operations when hostname
aliases are used. Workaround: Use fully qualified domain names when you install
the Data Fabric through the Installer. Run
hostname -f
to verify that the fully qualified domain name is returned. If the command returns a short hostname, the issue will persist. - ES-77: During an upgrade from EEP 6.x
to EEP 7.0.0 or EEP 7.0.1, some monitoring components do not get
updated because of an error in the fourth digit of the package version. This issue can
occur during manual upgrades or upgrades performed using the Installer. The affected
components can include any or all of the following:
- Elasticsearch
- Fluentd
- Grafana
- Kibana
- FLUD-51: In the
fluentd.conf
file, the log file name for Kibana iskibana.log
. The file name is incorrect; the file name should bekibana_daemon.log
. As long as thefluentd.conf
file has the incorrect log-file name, you will not see Kibana log entries in Elasticsearch. Workaround: In thefluentd.conf
file, changekibana.log
tokibana_daemon.log
, and restart Fluentd. - KIB-45: The Kibana default index and example dashboard are not loaded at system
startup. Workaround: Run the following command, and restart
Fluentd:
chmod +x /opt/mapr/kibana/kibana-6.8.8/bin/es_mgmt.sh
Resolved Issues
- None.