You must be connected to the Cisco AppDynamics Events Service to send data to it. Cisco AppDynamics uses API keys and connection URLs to establish connections between components. 

You can configure these connection settings on the Controller Settings page of the Admin Console (see Access the Administration Console). The following sections describe the required connection settings for Database Visibility, Analytics, and End User Monitoring. 

Connect to the Events Service

Database Visibility and Analytics Connection Settings

The Database Visibility module stores some of its data (such as wait state information and query information) in the Events Service. The Database Visibility module is the Database Monitoring product, which is already bundled with the controller. If you have both Analytics and Database Visibility installed, we recommend that they share an Events Service instance or cluster instance. 

To connect these modules to the Events Service, open the Admin Console > Controller Settings and set values for the following properties:

  • Set appdynamics.on.premise.event.service.key to the corresponding key in the properties file for Database Visibility.
  • Set appdynamics.on.premise.event.service.url to the Events Service endpoint URL.
  • Set appdynamics.non.eum.events.use.on.premise.event.service to true.

To set up the properties files required for Database Visibility:

  1. Make note of the appdynamics.on.premise.event.service.key value from the Admin Console.
  2. Open the file called events-service-api.properties, which you can find under the Events Service conf directory. 
  3. In the Events Service file, events-service-api-store.properties, ensure that the On-Premise Events key matches with the values of ad.accountmanager.key.controller and ad.accountmanager.key.mds 
    1. See Configure the Events Services Properties for details. 
  4. Stop and start the Analytics Service through the Enterprise Console or command line to pick up the new values.

End-User Monitoring Connection Settings

  1. Open Admin Console > Controller Settings 
  2. Locate eum.es.host and verify it is set to the proper Events Service endpoint URL. 

  3. Navigate to the <EUM_HOME>/eum-processor/bin/eum.properties file

  4. Set the following property values to connect the EUM to the Events Service: 

    Sample

    analytics.enabled=true
analytics.serverScheme=http
analytics.serverHost=events.service.hostname
analytics.port=9080
analytics.accountAccessKey=1a59d1ac-4c35-4df1-9c5d-5fc191003441
    CODE
  5. Open the Admin Console > Controller Settings 
  6. Set the eum.es.host to the Events Service endpoint URL.

The value of appdynamics.es.eum.key will automatically be set to the property analytics.accountAccessKey of the file <EUM_HOME>/eum-processor/bin/eum.properties. 

Proxy Connection Settings

If you are connecting Database Visibility or Analytics through a proxy, you must set values for the following properties:

  • appdynamics.on.premise.event.service.proxy.host
  • appdynamics.on.premise.event.service.proxy.port
  • appdynamics.on.premise.event.service.proxy.user
  • appdynamics.on.premise.event.service.proxy.password.file
  • appdynamics.on.premise.event.service.proxy.use.ssl

If you are connecting EUM through a proxy, you must set values for the following properties:

  • appdynamics.controller.http.proxyHost
  • appdynamics.controller.http.proxyPort
  • appdynamics.controller.http.proxyUser
  • appdynamics.controller.http.proxyPasswordFile