ServiceNow AppDynamics Integration Guide

Architecture Overview

Implementation Steps

(function process(request, response) {
    try {
        var payload = request.body.data;
        var incident = new GlideRecord('incident');
        incident.initialize();
        incident.short_description = payload.displayName || 'AppDynamics Alert';
        incident.description = payload.summaryMessage || '';
        incident.urgency = payload.severity === 'ERROR' ? 1 : 2;
        incident.impact = payload.severity === 'ERROR' ? 1 : 2;
        incident.assignment_group = 'Application Support';
        incident.u_appdynamics_alert_id = payload.id;
        incident.u_application_name = payload.affectedEntityName;
        var sys_id = incident.insert();
        
        response.setStatus(201);
        response.setBody({incident_number: incident.number, sys_id: sys_id});
    } catch (e) {
        response.setStatus(500);
        response.setBody({error: e.getMessage()});
    }
})(request, response);

{
  "displayName": "${displayName}",
  "summaryMessage": "${summaryMessage}",
  "severity": "${severity}",
  "affectedEntityName": "${affectedEntityName}",
  "deepLinkUrl": "${deepLinkUrl}",
  "eventTime": "${eventTime}",
  "applicationName": "${applicationName}",
  "tierName": "${tierName}",
  "nodeName": "${nodeName}",
  "id": "${id}"
}

// Test script to validate AppDynamics connectivity
var flow = new GlideFlowEngine();
var inputs = {};
inputs.connection_alias = 'AppDynamics Connection';
inputs.application_name = 'YourTestApplication';

try {
    var result = flow.startFlow('AppDynamics Application Health Check', inputs);
    gs.info('AppDynamics integration test successful: ' + result);
} catch (e) {
    gs.error('AppDynamics integration test failed: ' + e.getMessage());
}

Common Use Cases

Troubleshooting

Pro Tips

• →Implement incident deduplication logic in your Scripted REST API by checking for existing incidents with the same AppDynamics Alert ID before creating new records. Use GlideRecord queries with indexed fields to prevent duplicate incidents from rapid-fire AppDynamics policy executions. This prevents alert storms from overwhelming ServiceNow with redundant incident records.
• →Configure AppDynamics HTTP Request Template payload to include the ${deepLinkUrl} variable and map it to a ServiceNow URL field for one-click navigation from incidents back to AppDynamics dashboards. This dramatically improves troubleshooting efficiency by providing instant context switching between ITSM and monitoring tools.
• →Use ServiceNow Transform Maps instead of Scripted REST APIs for high-volume AppDynamics integrations to improve performance and maintainability. Configure the transform map to handle AppDynamics webhook payloads and leverage built-in error handling, field mapping, and data validation capabilities.
• →Implement circuit breaker patterns in Flow Designer workflows that query AppDynamics APIs by adding conditional logic to skip API calls when previous calls have failed consecutively. This prevents integration failures from cascading and impacting ServiceNow performance during AppDynamics maintenance windows.
• →Create custom ServiceNow reports that correlate AppDynamics incident volume with change management activities by joining incident and change request tables on time-based criteria. This provides valuable insights into application stability trends and change success rates.
• →Configure AppDynamics Business Journey monitoring integration with ServiceNow to automatically create major incidents when end-user experience degrades across multiple applications. Use the AppDynamics spoke to query Business Journey health and implement sophisticated correlation rules in Flow Designer.

Known Limitations

• —AppDynamics Controller API rate limits restrict spoke Actions to 100 requests per minute per user, which may cause throttling during high-volume incident creation or bulk data enrichment scenarios. Consider implementing queuing mechanisms or staggered API calls for large-scale integrations. The Integration Hub AppDynamics spoke does not include built-in retry logic for rate-limited requests.
• —The ServiceNow Integration Hub AppDynamics spoke requires Professional or Enterprise Integration Hub licensing and is not available with Starter licenses. Organizations with Starter licenses must implement custom REST integrations using Scripted REST APIs and RESTMessageV2 classes. The spoke also requires quarterly updates to maintain compatibility with AppDynamics Controller API changes.
• —Real-time performance data synchronization between AppDynamics and ServiceNow introduces latency of 2-5 minutes depending on polling frequency and API response times. Critical alerts requiring immediate response should use AppDynamics native notification channels in addition to ServiceNow integration. The spoke Actions do not support streaming data or WebSocket connections for true real-time updates.
• —AppDynamics webhook payloads have a maximum size limit of 1MB, which may truncate large application topology or metric datasets when sent to ServiceNow. Complex application environments with extensive dependency mapping may require multiple API calls or filtered data sets to stay within payload limits. Custom field mapping may be required for AppDynamics installations with non-standard configuration schemas.

Frequently Asked Questions