AppDynamics
Send monitoring events from AppDynamics to BigPanda.
| Supported Versions | Type | Authentication Type |
|---|---|---|
| up to v21; On-Premise, Dedicated SaaS Deployments - For previous versions, an Action Script version of the integration is available. | Webhook | Org Bearer Token |
The integration uses a custom HTTP action, policy, and template in AppDynamics. When an event occurs and a policy fires the action, AppDynamics sends an HTTP request to BigPanda as defined by the template. BigPanda then processes and correlates the alert data to create and maintain up-to-date incidents in BigPanda.
The Open Integration Manager is available for use with AppDynamics. For more information, see the Open Integration Manager documentation.
Key Features
- Is resource-efficient for the AppDynamics controller; reuses one server thread for all alerts
- Uses the Custom HTTP action feature in AppDynamics alerts
Install the Integration
Administrators can install the integration by following the on-screen instructions in BigPanda.
AppDynamics Data Model
BigPanda normalizes alert data from AppDynamics into tags. You can use tag values to filter the incident feed and to define filter conditions for Environments. The primary and secondary properties are also used during the deduplication and correlation processes.
Standard Tags
| Tags | Description |
|---|---|
application | Name of the business application |
message | Summary of the notification. For example: health rules have been violated |
severity | Severity of the alert in AppDynamics |
incident | AppDynamics incident identifier |
app dynamics_url | URL to the Controller UI in AppDynamics for this event |
event_guid | Unique identifier for the AppDynamics event |
appd_event_type | What type of event occurred Options include: Health-rule or Error-event |
affectedEntities | List of the affected entities This integration supports 4 types of entities: Application, Node, Tier, and Business Transaction. For entities not already mapped to existing tags, BigPanda adds name and ID tags for the entity |
object | Concatenation of the business application, tier name, and node name primary_property* |
title | Concatenation of the business application, tier name, and node name, delimited by colons. For Example “Application: Tier: Node” |
notes | Notes describing the event that was triggered |
The BigPanda AppDynamics integration files events into one of two classifications: Health Rule events and Error events. These classifications have tags that are specific to that type of event.
Health Rule Tags
| Tags | Description |
|---|---|
health_rule | Name of the health rule that was violated secondary_property* |
incident_id | Name of the incident that was triggered |
Error Event Tags
| Tags | Description |
|---|---|
error_name | Normalized name of the error that occurred |
error_display_name | AppDynamics display name for the error that occurred. secondary_property* |
Custom Tags
The AppDynamics alert allows you to add extra fields, to be included as tags on the BigPanda alert. If you wish to add a tag not included in the above list, add the tag to the HTTP request template and update the include_fields list to include the field. For a list of variables that can be used in the AppDynamics HTTP request template, please consult the Predefined Templating Variables section of the AppDynamics documentation.
For more information on adding custom tags to the final BigPanda alert, please see the in-app AppDynamics integration documentation.
Deactivate the Integration in BigPanda
If you want to stop sending data to BigPanda but don’t want to delete your integration, you can temporarily deactivate it.
To deactivate an integration:
- In BigPanda, navigate to the Integrations tab and select the desired integration from the list. This will open integration details on the right side of the window.
- At the top of the integration details, click the Active/Inactive toggle next to the application name to change the status of the integration.
Alert Resolution for Inactive Integrations
Any active alerts belonging to an inactive integration must be manually resolved or they will stay in the system until the auto-resolve window is reached.
Uninstall AppDynamics
You must delete the BigPanda action, policy, and template from AppDynamics to stop sending alerts to BigPanda via the AppDynamics Webhook integration.
Before You Start
Manually resolve any open incidents related to the integration to remove them from your incident feed. Optionally, remove any additional data in BigPanda. For example, modify or remove any Environments or AutoShare rules that reference the integration.
Procedure
- Log in to your AppDynamics controller.
- Go to Actions.
- Delete the BigPandaAlert action.
- Go to Application > Alert & Respond > Policies.
- Delete the BigPanda policy.
- Go to Alert & Respond > HTTP Request Templates.
- Click Delete beside the BigPandaAlertTemplate row.
Delete the Integration in BigPanda
- In BigPanda, navigate to the Integrations tab and select the desired integration from the list.
- In the integration details on the right of the page, click the trash icon, then confirm you want to delete the integration. The integration will then be removed immediately.
Alert Resolution for Deleted Integrations
All active alerts from the integration will be resolved after deletion.
️Data Removal
This procedure does not remove any data from the integrated system.
Action Script Version
For versions prior to AppDynamics 4.1, use this version of the BigPanda integration.
| Supported Versions | Type |
|---|---|
| .8, 4.x; On-premise, dedicated SaaS Deployments For versions 4.1 and up, the Webhook version of the integration is recommended | Action Script |
The integration uses a custom action script, custom.xml file, policy, and action in AppDynamics. Configuring this integration installs a custom action script and custom.xml file on the Controller. When an event occurs and a policy fires the action, AppDynamics sends information to BigPanda as described in the custom action script and custom.xml file. BigPanda then processes and correlates the alert data from AppDynamics to create and maintain up-to-date incidents in BigPanda.
Key Features
- Uses one thread per alert.
- Uses the custom action script feature.
Install the Action Script
Administrators can install the integration by following the on-screen instructions in BigPanda.
Uninstall the Action Script
If you previously installed the action script version of the integration, you can remove the BigPanda custom action from your AppDynamics instance to stop sending alerts to BigPanda.
- For every application you have configured in AppDynamics:
a. Go to Application > Alert & Respond > Policies.
b. Remove the BigPanda policy. - For every application you have configured in AppDynamics:
a. Go to Application > Alert & Respond > Actions.
b. Remove the BigPandaAlert custom action. - Edit
<CONTROLLER INSTALL ROOT>/custom/actions/custom.xmland remove these lines:
<action> <type>bigpanda-alert</type> <executable>bigpanda_alert.py</executable> </action>
- Remove the directory:
<CONTROLLER INSTALL ROOT>/custom/actions/bigpanda-alert.
The bigpanda-alert option remains in the custom actions list until the next time it reloads.
Release Notes
v3.0.0 (9/13/23)
- Added Open Integration Manager compatibility
- Tags from BigPanda can now be controlled
v2.0.0 (10/12/21)
- Error alert types now included
- Note Field Added
- Additional Tags Included
v1.0.0
- Initial release 🎉
Updated 5 months ago