VictorOps - Alerting Extension

This alerting extension is only meant for on-premise or dedicated controllers.

 

Use Case


VictorOps is an on-call management + incident notification platform. The VictorOps alerting extension enables AppDynamics to post AppDynamics events as custom alerts to VictopOps. The payload of the alert has a link to AppDynamics for a thorough diagnosis of the event.

 

Prerequisites

 

  • You should have a VictorOps Organization Key and Routing Key

 

Steps

 

Please use the victorops-alert_1.0.3.zip for controller version 3.x and victorops-alert_2.0.zip for controller version 4.x.  

 

  1. Download the VictorOps Alerting Extension zip from [AppDynamics Exchange](http://community.appdynamics.com/t5/AppDynamics-eXchange/idb-p/extensions)
  2. Unzip the victorops-alert.zip file into <CONTROLLER_HOME_DIR>/custom/actions/ . You should have <CONTROLLER_HOME_DIR>/custom/actions/victorops-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 <custom-actions> element.
<action>
    <type>victorops-alert</type>
     <!-- For Linux/Unix *.sh -->
    <executable>victorops-alert.sh</executable>
      <!-- For windows *.bat -->
    <!--<executable>victorops-alert.bat</executable>-->
  </action>

   If you don't have custom.xml already, create one with the below xml content

 

 <custom-actions>
      <action>
  	  <type>victorops-alert</type>
          <!-- For Linux/Unix *.sh -->
   	  <executable>victorops-alert.sh</executable>
        <!-- For windows *.bat -->
   	   <!--<executable>victorops-alert.bat</executable>-->
   </action>
</custom-actions>

  Uncomment the appropriate executable tag based on windows or linux/unix machine.

 

 4. Update the config.yaml file in <CONTROLLER_HOME_DIR>/custom/actions/victorops-alert/conf/ directory with the Organization Key, Routing Key. You can also configure the level of details sent to VictorOps.

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

 

	#VictorOps Org Key
	voOrganizationKey: ""
	
	#VictorOps Routing Key
	voRoutingKey: ""
	
	#scheme used (http/https)
	protocol: "https"
	
	#VictorOps host
	voAlertHost: "alert.victorops.com"
	
	#VictorOps url path
	voAlertUrlPath: "/integrations/generic/20131114/alert"
	
	#http timeouts
	connectTimeout: 10000
	socketTimeout: 10000
	
	#control level of details in VO alert
	showDetails: false

 

 

6. Installing Custom Actions:

 

    To create a Custom Action, first refer to the the following topics (requires login):
    * [Creating custom action]
    * [Build an Alerting Extension]

 

Now you are ready to use this extension as a custom action. In the AppDynamics UI, go to Alert & Respond -> Actions. Click Create Action. Select Custom Action and click OK. In the drop-down menu you can find the action called 'victorops-alert'.

 

 VictorOps Alert

victorops-alert.png

 

 

 

Contributing

   

Always feel free to fork and contribute any changes directly via GitHub

 

 Community

   

Find out more in the Community

 

 Support

  

For any support questions, please contact help@appdynamics.com.

  

Version:

2.0

Compatibility:

3.7+

Last Update:

05/21/2015

 

1.0.3 : Added policy_close events, fixed the jdk path.

2.0   :  Adding support for account information to support arguments passed in controller 4.0+

 

 

Note: This extension works only with a dedicated SaaS controller or an on-prem controller. Alerting extensions, currently do not support multi-tenant SaaS controllers. 

Attachments: