AppDynamics Alert Integration

Sync AppDynamics alerts to Flashduty via webhook for automated alert noise reduction.

In AppDynamics

I. AppDynamics Alert Push Configuration

Step 1: Configure FlashDuty Alert Channel

Find Alert Respond, select HTTP Request Templates, and click New to create an alert channel

In the template configuration, enter FlashDuty as the Name

In the Request URL section, select POST as the Method, and enter the integration push URL in Raw URL (enter the integration name on this page, and the URL will be generated after saving)

In the Payload section, select application/json as MIME Type and UTF-8 as Payload Encoding

Paste the following content in the Payload text box:

{
	"policy_name":"${policy.name}",
	"message": "${latestEvent.eventMessage}",
	"application_name": "${latestEvent.application.name}",
	"link": "${latestEvent.deepLink}",
	"incident_id": "${latestEvent.incident.id}",
	"details": {
		"event_id": "${latestEvent.id}",
		"event_name": "${latestEvent.displayName}",
		"event_time": "${latestEvent.eventTime}",
		"event_type": "${latestEvent.eventType}",
		"health_rule_name":"${latestEvent.healthRule.name}",
		"node_name": "${latestEvent.node.name}",
		"severity": "${latestEvent.severity}"
	}
}

Special Note (Optional Configuration)

Configuration: Custom Templating Variables

If you need to configure Custom Templating Variables, you can refer to the following JSON template. Here, custom_variables is a fixed format, and the variables within custom_variables are custom Variables. The names defined on the page should match the variable names referenced in the JSON template.

{
	"policy_name":"${policy.name}",
	"message": "${latestEvent.eventMessage}",
	"application_name": "${latestEvent.application.name}",
	"link": "${latestEvent.deepLink}",
	"incident_id": "${latestEvent.incident.id}",
	"details": {
		"event_id": "${latestEvent.id}",
		"event_name": "${latestEvent.displayName}",
		"event_time": "${latestEvent.eventTime}",
		"event_type": "${latestEvent.eventType}",
		"health_rule_name":"${latestEvent.healthRule.name}",
		"event_type_key": "${latestEvent.eventTypeKey}",
		"node_name": "${latestEvent.node.name}",
		"severity": "${latestEvent.severity}"
	},
	"custom_variables":{
		"host":"${host}"
	}
}

In the Response Handling Criteria section, set the Failure Criteria status code to 400 and the Success Criteria status code to 201

Click Save to complete

Step 2: Create Action

Select Actions in the left navigation bar, choose the application type you want to create for, and click Create

In the Create Action popup, select Make an HTTP Request and click OK

In the Create HTTP Action popup, enter a Name, select FlashDuty created in Step 1 as the HTTP Request Template, and click SAVE

Step 3: Use the Action Created in Step 2 in Alert Policies

Select Policies in the left navigation bar

Create or edit existing policies (configure alert rules as needed, alert rule configuration is omitted here)

In the Actions section of the policy configuration page, click add and select the Action created in Step 2

After completing other configurations, click Save to finish

II. Status Mapping

AppDynamics	Flashduty	Status
ERROR	Critical	Critical
WARN	Warning	Warning
INFO	Info	Info

AppDynamics Alert Integration

In Flashduty

Using Private Integration

Using Shared Integration

In AppDynamics

I. AppDynamics Alert Push Configuration

Step 1: Configure FlashDuty Alert Channel

Step 2: Create Action

Step 3: Use the Action Created in Step 2 in Alert Policies

II. Status Mapping

AppDynamics Alert Integration

In Flashduty#

Using Private Integration#

Using Shared Integration#

In AppDynamics#

I. AppDynamics Alert Push Configuration#

Step 1: Configure FlashDuty Alert Channel#

Step 2: Create Action#

Step 3: Use the Action Created in Step 2 in Alert Policies#

II. Status Mapping#

In Flashduty

Using Private Integration

Using Shared Integration

In AppDynamics

I. AppDynamics Alert Push Configuration

Step 1: Configure FlashDuty Alert Channel

Step 2: Create Action

Step 3: Use the Action Created in Step 2 in Alert Policies

II. Status Mapping