The Edwin AI AppDynamics Integration is a customer-hosted Python application that enables Edwin AI to ingest event data from AppDynamics using a polling-based mechanism. This integration enables Edwin AI to monitor application health, detect incidents, and enrich alerts using structured data retrieved from AppDynamics APIs.

The integration periodically queries AppDynamics for event and health violation data, transforms it into Common Event Format (CEF) of Edwin AI, and forwards it to Edwin AI for processing. All polling and data forwarding require prior configuration.

To set up the Edwin AI AppDynamics Integration, complete the following tasks:

1. Install the integration application in your infrastructure
2. Map data fields to the Edwin AI common format

Requirements for Configuring Edwin AI AppDynamics Integration

To install and configure your Edwin AI AppDynamics Integration, you need the following:

• AppDynamics API credentials (access token or client ID or secret)
• Access permissions to relevant AppDynamics APIs
• Outbound HTTPS access to the Edwin AI event ingestion endpoint
• Persistent storage for bookmarks

Installing and Configuring the Edwin AI AppDynamics Integration

1. In Python, navigate to your AppDynamics application directory.
2. Open the configuration file.
   For example, config.yaml or .env, depending on your deployment.
3. In the polling_frequency field, enter an interval in minutes or hours.
4. In the API Access Token field, enter your access token.
5. Enter your username and password.
6. In the Configuration field, enter the event types and severities you require Edwin AI to retrieve.
   For example: event_types: [APPLICATION_ERROR, AGENT_ERROR]
7. Set the edwin_endpoint field to the correct ingestion URL.
   For example: https://accountname.dexda.ai/integration/event/v1
8. Verify that the integration has read access to all required AppDynamics APIs.
   For example: /events, /healthrules
9. In the bookmark file field, set a persistent storage location to track the last successful polling state.
   This ensures that only new or updated data is processed and prevents duplicate event ingestion.
10. Select Save and start the integration.
11. Restart or launch the integration application to begin polling.

Mapping AppDynamics Data to Edwin AI Common Event Format

The following table lists how AppDynamics event fields map to Edwin AI CEF:

source	“AppDynamics”
sourceUrl	deepLinkUrl
timestamp	AppDynamics timestamp
eventCI	triggeredEntity.name
eventObject	Depends on event type
eventName	AppDynamics event name
eventDescription	AppDynamics event description

Health Rule Violation Mapping

The following table lists the field mappings for health rule violations:

source	“AppDynamics”
sourceUrl	deepLinkUrl
timestamp	startTimeInMillis
eventCI	affectedEntityDefinition.name
eventObject	affectedEntityDefinition.entityType
eventName	triggeredEntityDefinition.name
eventDescription	description