Configuring Notification Policies - Tutorial

Welcome to this tutorial on configuring notification policies in Appdynamics. Notification policies allow you to define the rules and settings for receiving alerts and notifications from your application monitoring system. By properly configuring notification policies, you can ensure that the right people are notified at the right time, enabling timely responses to critical events and issues within your application environment.

Step 1: Accessing Notification Settings

To configure notification policies in Appdynamics, follow these steps:

  1. Login to your Appdynamics account.
  2. Navigate to the "Settings" section.
  3. Select "Notifications" or "Notification Policies" to access the notification settings.

Step 2: Defining Notification Channels

Notification channels determine the method through which alerts and notifications are sent. Appdynamics supports various channels such as email, SMS, and third-party integrations. Here's an example of defining an email notification channel:

curl -X POST -H "Content-Type: application/json" -d '{ "name": "Email Channel", "type": "EMAIL", "recipients": [""] }'

In the above example, we define an email notification channel named "Email Channel" with the recipient's email address set to "".

Step 3: Creating Notification Policies

Notification policies specify the conditions under which alerts and notifications should be sent. You can define policies based on various criteria such as severity levels, health rules, or specific events. Here's an example of creating a notification policy:

curl -X POST -H "Content-Type: application/json" -d '{ "name": "High CPU Usage", "severity": "ERROR", "condition": "METRIC_CPU_USAGE > 90", "channels": ["Email Channel"] }'

In the above example, we create a notification policy named "High CPU Usage" that triggers an alert when the CPU usage metric exceeds 90%. The severity is set to "ERROR", and the associated notification channel is "Email Channel".

Common Mistakes

  • Not configuring notification policies for critical events or performance thresholds, resulting in delayed responses to issues.
  • Overlooking the importance of regularly reviewing and updating notification policies as the application environment evolves.
  • Not configuring multiple notification channels to ensure redundancy and reachability.

Frequently Asked Questions

  1. Can I configure different notification policies for different applications or tiers?

    Yes, Appdynamics allows you to define notification policies at the application or tier level. This flexibility enables you to tailor notifications based on the specific needs and criticality of each application or tier.

  2. Can I configure on-call schedules for notifications?

    Yes, Appdynamics provides the capability to set up on-call schedules for notifications. This ensures that alerts are routed to the appropriate person or team based on the designated schedule.

  3. Can I customize the content of alert notifications?

    Yes, Appdynamics allows you to customize the content of alert notifications by defining templates or using variables to include relevant information such as the name of the application, metric values, or event details.

  4. How can I test my notification settings?

    Appdynamics provides test notifications feature that allows you to send sample notifications to validate your configuration and ensure that alerts are being delivered to the intended recipients.

  5. Can I integrate Appdynamics with external incident management tools?

    Yes, Appdynamics provides integrations with popular incident management tools such as ServiceNow, JIRA, and PagerDuty. These integrations enable seamless ticket creation and automated incident management workflows when alerts are triggered.


In this tutorial, we explored the process of configuring notification policies in Appdynamics. By defining notification channels, creating notification policies, and setting up appropriate conditions and channels, you can ensure that you receive timely alerts and notifications for critical events within your application environment. This enables you to proactively respond to issues, maintain high application availability, and deliver a better user experience.