Pre-Upgrade Steps for Monitoring
Complete the following steps before you upgrade Monitoring Components with or without the Installer.
About this task
Before
performing the pre-upgrade steps, note these important considerations:
- The Monitoring upgrade is an offline upgrade and not a rolling upgrade.
- This upgrade procedure is customized for the Data Fabric implementation of the monitoring components. Because the Data Fabric implementation has a narrow focus and there are numerous components, the upgrade steps are simplified. Data Fabric upgrade documentation does not include all of the upgrade steps that are included in the vendor documentation for each component. Before starting the upgrade process, consider familiarizing yourself with the vendor-upgrade steps to determine if your environment requires extra measures to protect data and configurations.
- This upgrade sequence does not implement security in the Monitoring components. If the cluster you are upgrading is secure and you are upgrading to a new version of Elasticsearch, the security keys will be deleted when you upgrade the monitoring packages. You must regenerate the keys and copy them to the appropriate nodes after upgrading. The Post-Upgrade Steps for Data Fabric Monitoring provide links to the installation procedures containing this information.
Procedure
-
Before backing up configuration files, ensure that your Elasticsearch and
Kibana indexes are not affected by the upgrade:
NOTEThis step assumes that log monitoring is configured. You can skip this step if your cluster is not configured for log monitoring.
-
Before you upgrade metric monitoring components, create a backup of the
configuration files to a location outside your installation directory. The following configuration file-lists include
files that are commonly used for configuration and may not include every file
that you may have customized.
- Collectd configuration files:
- /opt/mapr/conf/conf.d/warden.collectd.conf
- /opt/mapr/collectd/collectd-<version>/etc/collectd.conf
- /etc/logrotate.d/collectd
- Grafana configuration files:
- /opt/mapr/conf/conf.d/warden.grafana.conf
- /opt/mapr/grafana/grafana-<version>/etc/grafana/grafana.ini
- /opt/mapr/grafana/grafana- <version>/etc/grafana/ldap.toml
- OpenTSDB configuration files:
- /opt/mapr/conf/conf.d/warden.opentsdb.conf
- /opt/mapr/opentsdb/opentsdb-<version>/etc/opentsdb/opentsdb.conf
- /opt/mapr/opentsdb/opentsdb-<version>/etc/opentsdb/logback.xml
- opt/mapr/opentsdb/opentsdb-<version>/bin/tsdb_cluster_mgmt.sh (This file is not automatically backed up.)
- Collectd configuration files:
-
Before you upgrade log monitoring components, create a backup of the following
files to a location outside your installation
directory. The following configuration file lists include files that are
commonly used for configuration and may not include every file that you may have
customized.
- Kibana configuration files:
- /opt/mapr/conf/conf.d/warden.kibana.conf
- /opt/mapr/kibana/kibana-<version>/etc/conf/kibana.js
- fluentd configuration files:
- /opt/mapr/conf/conf.d/warden.fluentd.conf
- /opt/mapr/fluentd/fluentd-<version>/etc/fluentd/fluentd.conf
- /opt/mapr/fluentd/fluentd-<version>/etc/fluentd/es_config.conf
- /opt/mapr/fluentd/fluentd-<version>/etc/fluentd/maprfs_config.conf
- /opt/mapr/fluentd/fluentd-<version>/etc/fluentd/grok-patterns
- /etc/logrotate/fluentd
- Elasticsearch configuration files:
- /opt/mapr/conf/conf.d/warden.elasticsearch.conf
- /opt/mapr/elasticsearch/elasticsearch-<version>/etc/elasticsearch/elasticsearch.yml
- /opt/mapr/elasticsearch/elasticsearch-<version>/etc/elasticsearch/logging.yml
- /opt/mapr/elasticsearch/elasticsearch-<version>/etc/elasticsearch/curator.yml
- /opt/mapr/elasticsearch/elasticsearch-<version>/etc/elasticsearch/curator_actions/delete_indices.yml (This file is not automatically backed up.)
- /opt/mapr/elasticsearch/elasticsearch-<version>/var/lib/MaprMonitoring/
(This directory is the default location for Elasticsearch index
data. You must back up this directory unless you specified a
non-default location using the
-ESDB
parameter withconfigure.sh
during installation.)
- Kibana configuration files:
-
Stop all monitoring services on the
cluster.