This migration method requires you to install the Events Service 23.x in the same node where the Events Service 4.5.x is installed. However, you must install the Events Service versions as two different platforms within a node using Enterprise Console. Therefore, this approach is called as colocation approach. In each Events Service nodes, the Events Service platforms have different installation paths and listener ports. This way the Events Service platforms share the same host but operate as different entities. Therefore, you don't need any special hardware for the migration. 

Use the migration utility to migrate data from Events Service 4.5.x to 23.x platform. This utility first migrates the existing Events Service data from Events Service 4.5.x to 23.x platform in every node. When any data or metadata is collected in the Events Service 4.5.x platform during migration, the migration utility does the following:

  1. Uses the timestamp to identify the delta data or metadata
  2. Copies the delta to the Events Service 23.x platform.
  3. Ensures that new data and metadata flows to the Events Service 23.x platform.

To migrate Events Service Data on a single or multi nodes, make sure to use the analytics-on-prem-es2-es8-migration-23.7.0-246-exec.jar utility. This utility is available with the Enterprise Console 23.7 and 23.9 versions.


System Requirements

The Events Service installation and data migration require the following configurations:

  • The disk size must be four times greater than the size of your current Events Service 4.5.x, or at least 75% of the disk space is available to accommodate the Events Service installation and the data migration.
    For instance, if the Events Service 4.5.x uses 1 TB, then a disk size of 4 TB is required. Alternatively, ensure that a minimum of 3 TB of disk space is free (which is 75% of the 4 TB needed).
  • Each Events Service node must have 16 CPU cores and 128 GB RAM.

Migration Process

The following table outlines the tasks to migrate data from Elasticsearch 2.4.1 to 8.10.x version:

Before you begin:

  • Back Up the Events Service Data.
  • Ensure you have free ports to install Events Service 23.x.
  • We recommend that you complete the migration activities in a pre-production environment before moving to the production environment.
Serial NumberSteps
1Download the Migration Utility
2Upgrade Enterprise Console to the latest version
3Prepare the Events Service for Migration
4Configure the Load Balancer
5Identify a cut-off point
6Migrate data using AppDynamics utility

Download the Migration Utility

  1. Download analytics-on-prem-es2-es8-migration-23.7.0-246-exec.jar.

    1. Install or upgrade Enterprise Console to 23.7.0/23.9.0. See Install the Enterprise Console.
    2. Navigate to <YOUR_EC_HOME>/appdynamics/platform/platform-admin/archives/events-service/. 
    3. Extract the events-service.zip file.
    4. Navigate to events-service/bin/migration to use the migration utility jar.

    5. Copy this utility to the computer where you decided to run the Events Service migration.

       If you upgrade the Enterprise Console to the latest, you cannot obtain the migration utility (analytics-on-prem-es2-es8-migration-23.7.0-246-exec.jar). So, we recommend you to create a new node and copy the migration utility to this new node.

  2. Install JDK 17 and SQLite 3.x on your machine where you have downloaded the migration utility. SQLite helps you to monitor the migration status.

Upgrade Enterprise Console

Upgrade the Enterprise Console to 23.11.0 or higher. For more information, see Upgrade the Enterprise Console.

Enterprise Console >=23.11.0 only supports multiple platforms. So, you must upgrade Enterprise Console to 23.11.x to migrate Events Service data within cluster nodes.


Prepare the Events Service for Migration

To migrate the data from Events Service 4.5.x to 23.x within in a single node, you must create a new platform for the Events Service 23.x with the different installation paths and ports.


Step 1: Create the Events Service 23.x Platform

  1. Log in to the Enterprise Console GUI.
  2. In Platforms, verify the Events Service 4.5.x nodes.
  3. In Platforms, select Create Platform.
  4. Select Custom Install.
  5. Name the Platform:
    1. Specify the Name for the Events Service 23.x platform.
    2. Specify a path to install Events Service 23.x. This path must be different from the Events Service 4.5.x.
  6. Select the newly created platform and add hosts and credentials.
    The hosts and credentials must be as same as the Events Service 4.5.x platform.

For more information, see Administer the Enterprise Console.

Step 2: Install Events Service 23.x

Install the Events Service 23.x on the new platform.

  1. Log in to the Enterprise Console GUI.
  2. Select the new platform you created for Events Service 23.x.
  3. Go to Events Service and click Install Events Service:
    1. In Target Version, select the latest Events Service build.
    2. Select the Prod profile.
    3. Verify the Data Directory path. This path should be different from the Events Service 4.5.x platform.

    4. Specify the unique port numbers and make sure they do not conflict with the Events Service 4.5.x platform.

      If you specify the same port numbers to the Event Service 4.5.x and 23.x platforms, the Events Service cluster will crash.

    5. In Hosts, select all the Events Service nodes.

    6. Click Submit.

Step 3 Update the Events Service Properties

You can update the properties in Events Service without stopping the Events Service cluster. However, some changes may take effect after the rolling restart of the cluster.

Update the following properties in the events-service-api-store.properties file: 

Description Properties
Enable the business journey (Optional)
ad.bizoutcome.enabled=false to true
CODE
Avoid agent restarts or modify properties in the Controller configurations.
ad.accountmanager.key.eum=<<COPY_SAME_KEY_VALUE_FROM_Events_Service_4.5.x>>

ad.accountmanager.key.controller=<<COPY_SAME_KEY_VALUE_FROM_Events_Service_4.5.x>>

ad.accountmanager.key.mds=<<COPY_SAME_KEY_VALUE_FROM_Events_Service_4.5.x>>

ad.accountmanager.key.ops=<<COPY_SAME_KEY_VALUE_FROM_Events_Service_4.5.x>>

ad.accountmanager.key.slm=<<COPY_SAME_KEY_VALUE_FROM_Events_Service_4.5.x>>

ad.accountmanager.key.jf=<<COPY_SAME_KEY_VALUE_FROM_Events_Service_4.5.x>>

ad.accountmanager.key.account_service=<<COPY_VALUE_FROM(ad.accountmanager.key.service)>>

ad.accountmanager.key.admin_service=<<COPY_VALUE_FROM(ad.accountmanager.key.service)>>

ad.accountmanager.key.service=<<COPY_SAME_KEY_VALUE_FROM_Events_Service_4.5.x>>
CODE

Set the Keystore path.

Update this property if SSL is enabled in the Events Service 4.5.x.

ad.dw.https.keyStorePath=<<Absolute path of JKS file>>
CODE

Set the truststore path.

Update this property if SSL is enabled in the Events Service 4.5.x.

ad.dw.https.trustStorePath=<<Trust store path of cacerts>>
CODE


Back up the events-service-api-store.properties in the following location:

<APPDYNAMICS_HOME>/conf/ directory
CODE
Restore this file after the migration is successful.


Configure the Load Balancer

Update the load balancer configuration with the Events Service 23.x ports. This configuration is required to receive data on Events Service 23.x. For more information, see Load Balance Events Service Traffic Overview.

Identify a Cut-off Point

This migration uses the cutover method where the data flow switches from the Events Service 4.5.x to 23.x platform. You may observe partial data loss for the active sessions or business transactions. Therefore, you must identify the non-peak hours to perform the cutover. Repeat the delta migration until the delta becomes small then end the cutover. This ensures that minimal business transactions data remains for migration after the cutover.

Migration Utility

After you prepare the Events Service platforms in each Event Service cluster nodes, proceed to use the AppDynamics migration utility. See Migrate Events Service Data Using a Node.