Upgrade Procedure

To upgrade the On-premises Events Service to >= 20.9.0, we recommend that you follow this procedure.

The Events Service version 20.9.0 is packaged with the Enterprise Console version 21.2.4 or newer.

If the incoming data load is heavy, you may expect delays in Step 3d during the data migration process.

Data Migration

If you choose not to migrate data, then continue with Steps 1 through 3c, and do not complete Step 3d.
If you choose to migrate your data then data conflicts in may occur in Step 3d.

Upgrade Completion

If the upgrade fails, then you should revert the Controller to the old cluster; data loss may occur.
If the upgrade succeeds, then you can delete the old cluster.

Prepare the machine instances:
1. Identify a utility machine running Linux, to run the Enterprise Console and data migration scripts. There are no strict hardware requirements
  
  Make sure that the older (source) Events Service cluster, new (target) Events Service cluster, and utility machine all reside on the same network.
2. Ensure the target Events Service cluster has similar or better hardware than that of the source Events Service cluster. Ensure that the operating system (OS) on the new machine has these settings:
  1. Increase the file descriptors limit in the /etc/security/limits.conf file, and then reboot the machine. Use ulimit -n to verify the value.
```
*                soft    nofile          66000
*                hard    nofile          66000
# End of file
```
    YML
  2. Set vm.max_map_count in the /etc/sysctl.conf file, and then reboot the machine. Use cat /proc/sys/vm/max_map_count to verify the value.
```
vm.max_map_count=262144
```
    YML
Set up the new staging cluster:
1. Download and install the latest Enterprise Console, which includes Events Service 21.2.4. See Downloads and Platform Installation Quick Start.
2. In the Enterprise Console, install the On-premises Events Service. See Install the Events Service on Linux.
3. Enable the load balancer. See Load Balance Events Service Traffic.
4. To enable the Secure Socket Layer (SSL) in the Events Service, see Enable the Events Service to Use SSL.
5. To configure the Events Service for data migration, complete this procedure:
  1. Enable HTTP port in events-service-api-store.properties:
```
ad.es.node.http.enabled=true
```
    YML
  2. Add the remote reindex whitelist in the events-service-api-store.yml file:
```
    - className: com.appdynamics.analytics.processor.elasticsearch.configuration.ElasticsearchConfigManagerModule
      properties:
          nodeSettings:
              cluster.name: ${ad.es.cluster.name}
              ...
              indices.fielddata.cache.size: ${ad.es.fielddata.cache.size}
              reindex.remote.whitelist: "<IP address to one of the nodes in older cluster>:9200"
```
    YML
  3. Restart the new Events Service cluster from the Enterprise Console.
Migrate the data:
1. See Use the Data Migration Tool to install and configure the data migration script on the utility instance.
2. Enter this command to migrate the metadata:
```
python main.py migrate metadata es2 es6
```
  BASH
3. Navigate to the Controller Admin page and set your Controller to the new Events Service. See Connect to the Events Service.
  
  If you choose to migrate your data, then proceed to Step 3d.
4. Enter this command to migrate data from the old cluster to the staging cluster:
```
python main.py migrate data es2 es6
```
  BASH

Download PDF

Upgrade the Events Service to >= 20.9.0

Upgrade Procedure