AppDynamics Application Performance Monitoring traces every transaction and builds real-time application topology. With this ServiceNow® App your instance will have the capabilities to have AppDynamics Map iQ data fed into ServiceNow®. You can then use this to correlate events within the Event Management component. You can also use this data to create incidents correlated back to the correct CI within Service Management.
The following AppDynamics entities will be exported to ServiceNow® CIs.
AppDynamics CMDB SyncApplication should be installed on your ServiceNow® instance. Please login to ServiceNow® Store for instructions. Please make sure that you follow the instructions under
This is a standalone jar file that should be executed as a java program from any machine. This machine should have connectivity to the AppDynamics Controller as well as the ServiceNow® Instance. Forward proxy is supported, please refer to section 3.6 for details.
appdynamics-cmdb-sync-$version.zipfrom the downloads section
url: The complete http/https url of the controller
name: Any name to identify the controller. This name will appear as the primary name identifier in ServiceNow®. If you have multiple controllers, please make sure that the name is unique
accountName: The Account Name of the controller. If the controller is installed as single tenant, the Account name will be
userName: The username of the controller
password: The clear text password for the controller. If you wish to set an Encrypted Password, set the properties
encryptionKey. Please refer to Encryption Support for details.
passwordEncrypted: The Encrypted Password. Please refer to Encryption Support section for details.
applications: This is a list of applications thet needs to be exported to ServiceNow® CMDB
url: The URL of the service now instance
userName: The user name of the ServiceNow® instance. The role x_apd_appdynamics.appdynamics_role should be assigned to the user.
password: The clear text password. To use the encrypted password, please refer to Encryption Support section
passwordEncrypted: The encrypted password. For more details, please refer to Encryption Support section
datasource: The name of the datasource. Do NOT edit this.
relation: This section identifies the relations that should be exported into ServiceNow®. No need to edit this.
The program can be executed as a java program with the command
java -jar appdynamics-cmdb-sync.jarLogin to ServiceNow® instance and refer to the AppDynamics menu item to view the data
The logs will be generated in the same directory in a folder named logs.
To enable debug logging, edit the file
conf/logback.xml and change the level of the logger
To avoid setting the clear text password in the config.yml, please follow the process to encrypt the password and set the encrypted password and the key in the config.yml
appdynamics-cmdb-sync.jar. Replace the
clearTextPasswordwith actual values.
java -jar appdynamics-cmdb-sync.jar ENCRYPT encryptionKey clearTextPasswordThe script will output the encrypted password.
config.yml. The username and password is optional, can be omitted non-authenticating proxy.
proxy: url: "http(s)://ip.of.proxy" username: "" password: "" ignoredHosts: ["localhost","127.0.0.1","domain.example.com"]
The events integration uses the HTTP Templates feature in the controller to push events to the ServiceNow® Events API. The details of the API can he found here. For more information on the HTTP templates, please refer to AppDynamics documentation
This document assumes that the user is familiar with the configuration of HealthRules, Policies and Actions in AppDynamics. If not, please refer to Alert and Respond
Please fill up the following values in the HTTP Request Template
<your-instance>with the id of the actual instance
httptemplate-events-integration.vm. Update the
controllerNamein the first line of the file. It should be the same value that you have set as the
For any questions or feature request, please contact AppDynamics Help.