Upgrade the Events Service

You must upgrade manually if you:

• Do not use the Enterprise Console to deploy the Events Service
• Upgrade Events Service nodes hosted on remote Windows machines. The Enterprise Console does not support remote operations on Windows.

If you upgrade to a version of the Events Service other than the latest, run the Enterprise Console installer for the desired Events Service version. 

Cisco AppDynamics On-Premises 24.x includes Events Service that uses Elasticsearch 8.10.4 version whereas, Events Service Cluster 4.5.x uses Elasticsearch 2.4.1 version. If your Events Service is running with 4.5.x, you must migrate data from Elasticsearch 2.4.1 to 8.10.4 version. Cisco AppDynamics provides a migration utility that helps you migrate the data. If your Events Service running with 23.x version, we recommend you to upgrade the Events Service to >=24.4.0.

Before the Upgrade

Cisco AppDynamics removed Search Guard from the on-premises Events Service version 4.5.2.20561. If your deployment requires Search Guard or a comparable feature, do not upgrade to this version of the Events Service.

See the Support Advisory for more details.

1. Download and install the new Enterprise Console.
2. Plan the order in which to upgrade platform components (not just Events Service).
3. Modify the events-service-api-store.properties file.
   • Replace the absolute path APPLICATION_HOME property in the file with an actual path.
   • This is required because while performing a discover and upgrade job, the Enterprise Console is unable to migrate the data directory for custom environment variables in the file. Failure to modify the file causes the upgraded Events Service to start with a new, blank data set.
4. Back up your events-service.vmoptions file.
   • This is required because the events-service.vmoptions file is not maintained when the Events Service is upgraded. After the upgrade completes, merge your backup copy of events-service.vmoptions into the new file.

Upgrade the Events Service

1. Run the upgrade Events Service command. 
2. Discover the Events Service nodes using the Enterprise Console.

Verify the Upgrade

Once the upgrade completes: 

1. The Events Service process should have restarted—verify its health status in the Enterprise Console GUI.
2. Merge your backup copy of the events-service.vmoptions file into the new copy of the file created by the upgrade.

Startup Script Paths

After an upgrade, you will find the Events Service startup script paths below:

<installDir>/appdynamics/events-service/processor/bin/events-service.sh

CODE

This may be different from their paths before the upgrade.