On this page:
Java 1.8 is required for events-service.exe to work.
To upgrade the Events Service manually:
Stop the Events Service processes:
conf\events-store-api-store.propertiesfile in the new Events Service directory. Depending on which type of deployment you are using, this involves inspecting and migrating settings from:
If you are upgrading from 4.2 to 4.3.x or a later version 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:
While in 4.3 or later, the file should look like this:
Configure the connection to the Events Service in the Controller, and get the Controller key for the Events Service configuration as follows:
Copy the value of the property to your clipboard. You will need configure this in the Events Service properties file next.
Configure the connection from the Events Service to the Controller:
In a terminal, navigate to the
conf\events-service-api-store.properties file for editing
Find the following property and replace
controller-key with the copied key:
Ensure that the following critical properties are configured appropriately in the events-service-api-store.properties file:
Move ad.es.node.unicast.hosts property in events-services-api-store.properties while upgrading from 4.2 to 4.3.x or later.
ad.es.path.homeproperty in the property file used to start up the Events Service.
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/
Restart the Events Service processes from the new directory:
nohup bin/events-service.sh start -p conf/events-service-api-store.properties &
bin\events-service.exe check-health -hp localhost:9081
curl -XGET localhost:9081/healthcheck?pretty=true
[appduser@controller-one events-service]$ bin/events-service.exe check-health -hp 192.168.33.22:9081 [2015-12-09T18:30:45,342-08:00] HV000001: Hibernate Validator 5.0.2.Final [2015-12-09T18:30:45,956-08:00] Individual statuses below: [2015-12-09T18:30:45,956-08:00] [192.168.33.22:9081] status is [200 OK] [2015-12-09T18:30:45,956-08:00] Overall status Healthy
Configure the connections from the Analytics Agent, EUM Server, or Database Monitoring agents to the Events Service, as described in Connect to the Events Service.
For information on performing these steps, see Install the Events Service on Windows.
If you upgrade to 4.4.x from 4.3.x or an earlier version, the commands to start and stop the Events Service change. See Administer the Events Service for more information.