PDFs


This page applies to an earlier version of the AppDynamics App IQ Platform.
See the latest version of the documentation.


Skip to end of metadata
Go to start of metadata

On this page:


This topic describes how to upgrade a scaled-out Events Service. The Events Service instance that is embedded with the Controller is upgraded automatically when you upgrade the Controller. For a scaled-out Events Service, you need to follow the steps here to upgrade the Events Service.

About the Upgrade

For an Events Service deployment installed with the Platform Administration Application, you can use the Platform Administration Application. You may also manually perform the upgrade.

The procedure requires the Event Service process to shut down. You cannot perform a rolling upgrade. 

Upgrade the Events Service with the Platform Administration Application

You can use the Platform Administration Application to upgrade the Events Service software on deployed nodes.

Upgrade the Events Service from 4.3 to 4.3.x

Upgrades can be performed on the Events Service page of the application or with the following commands:

  1. Navigate to the <Platform Administration Application home directory>/platform-admin directory.
  2. If it has been more than one day since your last session, you will have to log in with the following command:

    bin/platform-admin.sh login --user-name <admin_username> --password <admin_password>
  3. Stop the Events Service with the following command:  

    bin/platform-admin.sh stop-events-service <events-service-name>
  4. Apply the upgrade to the Events Service nodes with the following command: 

    bin/platform-admin.sh upgrade-events-service

After you upgrade the Events Service, upgrade the EUM server if it is part of your deployment. Then, upgrade the Controller.

Upgrade the Events Service from 4.2 to 4.3.x

To upgrade the Events Service software from 4.2 to 4.3.x, you will need to first download and install the new Platform Admin installer before performing the following steps:

  1. Create a platform as follows:

    bin/platform-admin.sh create-platform --name <platform_name> --installation-dir <platform_installation_directory>

    The installation directory is the directory where the application installs all platform components.

    To avoid any failures, do not use the 4.2 Platform Admin installation directory. Instead, provide a new/empty directory.

  2. Add the SSH key that the Platform Admin application will use to access and manage the Events Service hosts remotely. (See Create the SSH Key for more information): 

    bin/platform-admin.sh add-credential --credential-name <name> --type ssh --user-name <username> --ssh-key-file <file path to the key file>

    <file path to the key file> is the private key for the Platform Admin machine. The installation process deploys the keys to the Events Service hosts. 

     

  3. Add hosts to the platform, passing the credential you added to the platform: 

    bin/platform-admin.sh add-hosts --hosts es_host_1 es_host_2 es_host_3 --credential <credential name>
  4. Discover the Events Service nodes that are not yet integrated:

    bin/platform-admin.sh discover-events-service --installation-dir /opt/appdynamics/events-service --hosts es_host_1 es_host_2 es_host_3

    This command integrates the nodes into the Platform Admin and also upgrades them for on-premises Events Service.

  5. Update your Events Service property ad.accountmanager.key.controller in events-service/conf/events-service-api-store.properties so that it matches with the Controller setting  appdynamics.on.premise.event.service.key  in  /admin.jsp.

    The Platform Admin does not maintain nor sync the old key upon upgrade.

After you upgrade the Events Service, upgrade the EUM server if it is part of your deployment. Then, upgrade the Controller.

Upgrade the Events Service Manually

If you did not use the Platform Administration Application to deploy the Events Service, perform the following tasks to upgrade the Events Service manually. Note that Java 1.8 is required for events-service.exe to work.

  1. Download the Events Service distribution, events-service.zip, from the AppDynamics download site to the Events Service machine. 
  2. Stop the Events Service processes: 

    bin/events-service.sh stop
  3. Rename the existing Events Service directory, for example, to events-service-backup. 
  4. Unzip the Events Service distribution archive you downloaded to the location where you want the Events Service to run. 
  5. Migrate configuration changes from the properties files in the backup Events Service directory to the conf\events-store-api-store.properties file in the new Events Service directory. Depending on which type of deployment you are using, this involves inspecting and migrating settings from:
    • events-service-all.properties, or
    • events-service-api-store.properties

    If you are upgrading from 4.2 to 4.3.x, you must edit the events-service-api-store.properties file by replacing the port ranges [9300-9400] with :9300.

    For example, in 4.2, the events-service-api-store.properties file looks like this:

    ad.es.node.unicast.hosts=node1.example.com[9300-9400],node2.example.com[9300-9400],node3.example.com[9300-9400]

    While in 4.3, the file should look like this:

    ad.es.node.unicast.hosts=node1.example.com:9300,node2.example.com:9300,node3.example.com:9300
  6. Move ad.es.node.unicast.hosts property in events-services-api-store.properties while upgrading from 4.2 to 4.3.x.

  7. Verify that the new Events Service home directory exists.  The Event Service home directory is determined by the ad.es.path.home property in the property file used to start up the Events Service. 
    If the directory does not exist, create it.  For example, create the following directory:  :  /opt/appdynamics/events-service/appdynamics-events-service
  8. Move (do not copy) the old Events Service data directory to the new Events Service home directory directory. For example: 

    mv /opt/appdynamics/events-service-backup/appdynamics-events-service/data /opt/appdynamics/events-service/appdynamics-events-service/
  9. Restart the Events Service processes from the new directory:

    nohup bin/events-service.sh start -p conf/events-service-api-store.properties &
  10. Check the health API of the node.
    For information on performing these steps, see Install the Events Service on Windows.

 

 

  • No labels