Upgrade the Events Service

You can upgrade the Events Service either manually or by using the Enterprise Console for Windows or Linux.

Attention:

When you upgrade Events Service post migrating data to any version using Enterprise Console, certain configuration properties are reset to default values. Hence, you must backup the files before upgrading the Events Service. See Splunk AppDynamics On-Premises Known Issues.

This issue is not observed for fresh installations.

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.

Note: Splunk 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. Splunk 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.

Update the Events Service Keys

Ensure that the keys are matching in events-service-api-store.properties and the Administration Console (admin.jsp) to maintain synchronization. Go to the following locations to match and update the keys:

  • In the events-service-api-store.properties file, verify and update the keys in ad.accountmanager.key.controller if required.

  • In Administration Console (admin.jsp), verify and update the keys in appdynamics.on.premise.event.service.key if required.