oncall-engine/docs/sources/configure/integrations/references/appdynamics/index.md
Jack Baldry 9ae442faa6
Replace docs/reference shortcode with ref URIs (#4301)
You can use `ref` URIs in admonitions (or any shortcodes) because they
are inline and not subject to the issues noted in the [`admonition`
shortcode](https://grafana.com/docs/writers-toolkit/write/shortcodes/#code-shortcode:~:text=to%20core%20understanding.-,WARNING,For%20more%20information%2C%20refer%20to%20Markdown%20Reference%20Links%20in%20Shortcodes.,-Examples).

The `ref` URIs perform the same pattern matching as `docs/reference` but
don't require the use of reference-style links and the destinations are
ordinary (full) URLs that can include version substitution. Unlike
`docs/reference`, the implementation doesn't use `relref` so you don't
have to be careful with omitting trailing slashes and the links will
follow redirects.

Documentation:
https://grafana.com/docs/writers-toolkit/write/links/#link-from-source-content-thats-used-in-multiple-projects

To check the links, refer to the deploy preview in
https://github.com/grafana/website/pull/19630.

Signed-off-by: Jack Baldry <jack.baldry@grafana.com>

---------

Signed-off-by: Jack Baldry <jack.baldry@grafana.com>
2024-07-29 14:13:24 +00:00

4.8 KiB

title menuTitle description weight keywords labels canonical aliases refs
AppDynamics integration for Grafana OnCall AppDynamics AppDynamics integration reference material for Grafana OnCall. 0
OnCall
Integrations
Alerts
AppDynamics
Notifications
products
cloud
https://grafana.com/docs/oncall/latest/configure/integrations/references/appdynamics
/docs/grafana-cloud/alerting-and-irm/oncall/configure/integrations/references/appdynamics
/docs/grafana-cloud/alerting-and-irm/oncall/integrations/appdynamics
add-appdynamics/
../integrations/
complete-the-integration-configuration user-and-team-management
pattern destination
/docs/oncall/ /docs/oncall/<ONCALL_VERSION>/configure/integrations/integration-management/#customize-the-integration
pattern destination
/docs/grafana-cloud/ /docs/grafana-cloud/alerting-and-irm/oncall/configure/integrations/integration-management/#customize-the-integration
pattern destination
/docs/oncall/ /docs/oncall/<ONCALL_VERSION>/manage/user-and-team-management/
pattern destination
/docs/grafana-cloud/ /docs/grafana-cloud/alerting-and-irm/oncall/manage/user-and-team-management/

AppDynamics integration for Grafana OnCall

{{< admonition type="note" >}} This integration is available exclusively on Grafana Cloud. {{< /admonition >}}

The AppDynamics integration for Grafana OnCall handles health rule violation events sent from AppDynamics actions. The integration provides grouping and auto-resolve logic via customizable alert templates.

Configuring Grafana OnCall to Receive Alerts from AppDynamics

  1. In the Integrations tab, click + New integration.
  2. Select AppDynamics from the list of available integrations.
  3. Enter a name and description for the integration, click Create
  4. A new page will open with the integration details. Copy the OnCall Integration URL from HTTP Endpoint section. You will need it when configuring AppDynamics.

Configuring AppDynamics to Send Alerts to Grafana OnCall

Create a new HTTP Request Template in AppDynamics to send events to Grafana OnCall using the integration URL above.

Refer to the AppDynamics documentation for more information on how to create HTTP Request Templates.

Use the following values when configuring a new HTTP Request Template:

  • Request URL:

    • Method: POST
    • Raw URL: OnCall Integration URL from previous section
  • Authentication:

    • Type: None
  • Payload:

    • MIME Type: application/json
    • Template:
    {
      "event": {
        "eventType": "${latestEvent.eventType}",
        "id": "${latestEvent.id}",
        "guid": "${latestEvent.guid}",
        "eventTypeKey": "${latestEvent.eventTypeKey}",
        "eventTime": "${latestEvent.eventTime}",
        "displayName": "${latestEvent.displayName}",
        "summaryMessage": "${latestEvent.summaryMessage}",
        "eventMessage": "${latestEvent.eventMessage}",
        "application": {
          "name": "${latestEvent.application.name}"
        },
        "node": {
          "name": "${latestEvent.node.name}"
        },
        "severity": "${latestEvent.severity}",
        "deepLink": "${latestEvent.deepLink}"
      }
    }
    
  • Response Handling Criteria:

    • Success Criteria: Status Code 200
  • Settings:

    • One Request Per Event: Enabled

After setting up a template, create a new action in AppDynamics and select the template you created earlier. Now you can configure policies to trigger the action when certain events occur in AppDynamics. When configuring a policy, select the following events to trigger the action:

Health Rule Violation Started - Warning
Health Rule Violation Started - Critical
Health Rule Violation Continues - Warning
Health Rule Violation Continues - Critical
Health Rule Violation Upgraded - Warning to Critical
Health Rule Violation Downgraded - Critical to Warning
Health Rule Violation Ended - Warning
Health Rule Violation Ended - Critical
Health Rule Violation Canceled - Warning
Health Rule Violation Canceled - Critical

After setting up the connection, you can test it by sending a test request from the AppDynamics UI.

Understanding How Alerts Grouped and Auto-resolved

Grafana OnCall provides grouping and auto-resolve logic for the AppDynamics integration:

  • Alerts created from health rule violation events are grouped by application and node name
  • Alert groups are auto-resolved when the health rule violation is ended or canceled

Complete the Integration Configuration

Complete configuration by setting routes, templates, maintenances, etc. Read more in this section