This page applies to an earlier version of the AppDynamics App IQ Platform.
For documentation on the latest version, see the 4.4 Documentation.


On this page:


Your Rating:
Results:
PatheticBadOKGoodOutstanding!
55 rates
This topic describes how to upgrade your on-premise analytics and EUM storage node from a previous version. Before 4.1, this node was called the Analytics Processor. It is now called the Events Service.  

The following steps describe how to upgrade from this earlier version running under the "analytics-all" configuration for the data storage node. Analytics-all is a YAML-specified configuration for running the storage node as a single node. 

Upgrading from the Analytics Processor (pre-4.1 Events Service) to the 4.1 Events Service

  1. Shut down the Analytics Processor: 

     analytics-processor/bin/analytics-processor stop
  2. Download the 4.1 Events Service distribution file, events-service.zip.
  3. Unzip the Events Service ZIP file to the location where you want to install the Events Service, such as /opt/appdynamics/. This creates a folder called events-service in the /opt/appdynamics/ directory
  4. Move (do not copy) the existing Analytics Processor directory to the Events Service directory. For example:  

    mv /opt/appdynamics/analytics-processor/appdynamics-analytics/ /opt/appdynamics/events-service
  5. Copy the values of the following properties from /opt/appdynamics/analytics-processor/conf/analytics-all.properties to their corresponding properties in /opt/appdynamics/events-service/conf/events-service-all.properties:

    ad.es.cluster.name=appdynamics-analytics-cluster
    ad.accountmanager.key.eum=XX
    ad.accountmanager.key.controller=YY
    ad.accountmanager.key.ops=ZZ
  6. Also set the value of the ad.es.path.home property to the new path of the Events Service. For example: 

    ad.es.path.home=/opt/appdynamics/events-service/appdynamics-analytics
  7. Verify the setting that specifies the Events Service URL for the Controller. In previous versions, this value was set in the domain.xml file for the Controller, but is now a global setting in the administration console. To verify the setting:

    1. Open the Administration Console, as described in Access the Administration Console

    2. Search for the following property:

      appdynamics.analytics.server.store.url
    3. Verify that the setting has the correct URL for your Events Service host, including the API-Store port; for example, http://<hostname>:9080
  8. From the Events Service home directory, start the Events Service processes using the events-service-all YAML file:

    bin/events-service.sh start -y conf/events-service-all.yml -p conf/events-service-all.properties 
  9. From the Controller UI, ensure that the existing data appears in the Analytics UI. 

Upgrading from 4.1.x

The following steps describe how to upgrade the Events Service software for a manually maintained Events Service installation.

You should perform the following steps on each Events Service node in your deployment. The procedure requires the Event Service process to be briefly shut down. If you have deployed the Events Service in a cluster, you can perform the upgrade procedure as a rolling upgrade, avoiding service downtime. As a rolling upgrade, you upgrade each machine while the other cluster nodes continue to respond to client requests.    

  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 equivalent configuration file in the new directory. Depending on which type of deployment you are using, this involves inspecting and migrating settings between either:
    • events-service-all.properties, or
    • events-service-api-store.properties and events-service-zookeeper.properties
  6. Move (do not copy) the old Events Service data directory to the new data directory. The new location should be the new Events Service home directory. (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). For example, given an Events Service home under /opt/appdynamics/events-service/, the command would be:

    mv /opt/appdynamics/events-service-backup/data /opt/appdynamics/events-service/appdynamics-events-service/
  7. Restart the Events Service processes from the new directory and check the health API of the node. For information on performing these steps, see Install the Events Service on Linux or Install the Events Service on Windows.

 

 

  • No labels