AppDynamics Alerting Extension for use with HP Service Manager

Use Case

HP Service Manager (HPSM) now part of MicroFocus is a IT service management (ITSM) Tool using ITIL framework providing a web interface for Corporate changes, releases and interactions supported by a Service Catalog and CMDB. AppDynamics integrates directly with HPSM to create tickets in response to alerts. With the HPSM integration you can leverage your existing incident management infrastructure to notify your operations team to resolve performance degradation issues.

Note: This extension works with both AppDynamics Health Rule Violation events and Other Events. Auto close of incidents is only for Health Rule Violations and Other Events incidents are not auto closed.


To post events to HPSM an Operator User should have restful capability. For details refer to HP Service Manager Web Services document.

Installation Steps

  1. Download the zip from the GitHub RELEASES page

  2. Unzip the file into <CONTROLLER_HOME_DIR>/custom/actions/ . You should have <CONTROLLER_HOME_DIR>/custom/actions/hpsm-restapi-alert created.

  3. Check if you have custom.xml file in <CONTROLLER_HOME_DIR>/custom/actions/ directory. If yes, add the following xml to the element.

    	<!-- For Linux/Unix *.sh -->
    	<!-- For windows *.bat -->
    	If you don't have custom.xml already, create one with the below xml content.
    	Uncomment the appropriate executable tag based on windows or linux/unix machine.
       	<!-- For Linux/Unix *.sh -->
          <!-- For windows *.bat -->
  4. Update the config.yml file in <CONTROLLER_HOME_DIR>/custom/actions/hpsm-restapi-alert/conf/ directory with the rest URL, username, password and HPSMVersion. The rest url is different from SOAP URL for HP Service Manager and is new addition. This integration is compatible only with Rest URL. You can also configure the default HPSM fields like AssignmentGroup, Assignee, Area, company, category. If you have specific fields in HPSM which have values dependent on AppDynamics Applications such AssignmentGroup, Service, etc, then create a mapping csv file and place it in conf folder. Mention the csv file path name in config.yml. The csv file should have the first column as Application. There should not be duplicate column names in the csv file.

  5. Check if the version of java in your environment is 1.8 and above. If not download the latest 1.8 Java and provide the path in the hpsm-alert.bat/ as applicable



Please make sure to not use tab (\t) while editing yaml files. You may want to validate the yaml file using a yaml validator

	url: "http://<HPSM Hostname>:<REST Service Port>/SM/9/rest/incidents"
	#HPSM Rest User (Basic Authentication)
	username: "UserName"
	#HPSM Password, provide password or passwordEncrypted and encryptionKey.
	passwordEncrypted: "EncryptypedPassword"
	encryptionKey: "KEY"
	#HPSM Version
	hpsmVersion: "9.41"
	#Close notes text to be posted when resolving the incident
	closeNotesText: "This incident is resolved"
	#Proxy server URI
	#Proxy server user name
	#Proxy server password
	#HPSM User Specific
	#Please define your HPSM specific fields here like AssignmentGroup, Assignee, Area, Category and Company.
	#The name should be a valid Incident table's column name.
	#Do not add properties Title, Description, JournalUpdates, Impact and Urgency here, as they are added by the extension automatically.
	#If you have mapping of service and assignment group to AppD applications, then add them to CSV file and provide path in applicationFieldMapping
	   - name: "Assignee"
	     value: "test.user"
	   - name: "Area"
	     value: "Automated Ticketing"
	   - name: "Company"
	     value: "AppDynamics"
	   - name: "Category"
	     value: "incident"
	#If you have application specific field mappings, such as service or AssignmentGroup, provide the filename. If not leave blank.
	applicationFieldMapping: "appFields.csv"

Credentials Encryption

Please visit this page to get detailed instructions on password encryption. The steps in this document will guide you through the whole process.

HPSM Ticket

Open Ticket


Ticket Activity

Resolve Ticket

Close Ticket


For any questions or changes or feature request, please contact Alakshya M.


This alerting extension is based on the existing ServiceNow API Alerting Extension. Thanks to the authors of the extension!