AppDynamics Application Performance Monitoring traces every transaction and builds real-time application topology. With this ServiceNow® integration your instance will have the following capabilities:
The following AppDynamics entities will be imported into the AppDynamics for ServiceNow application in ServiceNow:
This integration has two components to download and install:
AppDynamics for ServiceNow Application should be installed on your ServiceNow® instance. Please login to ServiceNow® Store and search for “AppDynamics” for instructions. Please make sure that you follow the instructions under System Requirements and Other Requirements sections of this document.
AppDynamics for ServiceNow Application will create the following custom tables in your ServiceNow instance to represent these AppDynamics entities:
|AppDynamics Entity||ServiceNow Table Created|
This is a standalone JAR file that should be executed as a java program from any machine. Included in the JAR is a small web server which has a simple web application to configure the integration. The integration can also be run in command line only mode. The machine running the Data Sync Utility application must have connectivity to the target AppDynamics Controller as well as the target ServiceNow® Instance.
appdynamics-cmdb-service-$version.zipfrom the downloads section
sudo ln -s /path/to/appdynamics-cmdb-service/appdynamics-cmdb-service.jar /etc/init.d/appdynamics-cmdb-service sudo /etc/init.d/appdynamics-cmdb-service startThe java options can be configured in the file `$HOME/appdynamics-cmdb-service.conf`
%$HOME%/bin/appdynamics-cmdb-service-win.exe installThe java options can be configured in the file `%$HOME%/bin/appdynamics-cmdb-service-win.xml` The logs are created in the `$HOME/logs` directory.
java -Xms512m -jar /path/to/appdynamics-cmdb-service.jarThe application logs are created in the `$HOME/logs` directory
deFAultPwd4P1atfrm. This can be overridden by the java startup property
-Dplatform.password=welcome. Please refer the section
Server Optionsfor more details.
$HOME/appdynamics-cmdb-service.conf. Add the params to
$HOME/bin/appdynamics-cmdb-service-win.xmlAdd the params to
-Dplatform.security.enabled=true # This will create a local login with the following credentials. -Dplatform.username=user -Dplatform.password="deFAultPwd4P1atfrm" -Dplatform.security.encryption-key=mykey -Dplatform.security.encryption-salt=mysaltThe
The integration supports synchronization of one or more ServiceNow instances with one or more AppDynamics controllers.After logging in to the Sync Utility, click the “Service Model Integration” left hand menu bar
Once the synchronization is completed you may log in to ServiceNow® instance and select the AppDynamics menu item to view the tables and data associated with the integration.
Read Only Userrole
The logs will be generated in the same directory as the installed application in a directory named
Download Server Logs
conf/log4j2.xmland change the level of the logger
DEBUGlogs can be enabled from the UI also. Please click on the help icon on the top right corner of the screen and select
Configure Logging. Enter the package name as
com.appdynamicsand duration of 5 minutes
If you encounter any Read Timeout errors while doing the sync
60,000. If needed increase it to an even higher value
conf/application.propertiesin the installation directory. This change requires a restart of the server
This section assumes that the user is familiar with the configuration of HealthRules, Policies and Actions in AppDynamics. If not, please refer to Alert and Respond
The events integration uses the HTTP Templates feature in the controller to push events to the ServiceNow® Events API. The details of the Events API can be found here. For more information on the HTTP templates, please refer to HTTP Request Actions and Templates documentation.
Log in to the web UI for the AppDynamics-ServiceNow Data Sync Utility. Upon logging in click the “Service Model Integration” left-hand menu bar
This can be done from the “Alert & Respond” top menu in your AppDynamics controller. By creating an Action, and applying that action to a policy which specifies a health rule and action. To create the new Action:
<your-instance>with the id of the actual instance
event-request-template.vm. Update the
controllerNamein the first line of the file. It should be the same value that you have set while adding the AppDynamics Controller
Namein the Sync Utility.
For any questions or feature request, please contact AppDynamics Help.
3.0.0 Integration into Operational Intelligence and MetricBase
3.0.1 Commented “Node to hardware” functionality
3.0.2 Fixes for connection leaks