On this page:

Related pages:

Your Rating:
Results:
PatheticBadOKGoodOutstanding!
16 rates

There are two ways to configure policies:

  • Use the Policy Setup Wizard for simple policies that send an email notification when a health rule is violated.
  • Configure the policy manually for anything more complicated.

Permissions

To configure policies, you need the Configure Policies permission.

Policy Setup Wizard

For simple policies, in the Controller UI, click Alert & Respond > Policies > Policy Setup Wizard.

To create a notification policy, you must set up an SMTP server and supply an email address. The policy is then created.

To modify the policy later, select the policy and click the Edit button.

Create Policy Manually

To create a policy manually, in the Controller UI, click Alert & Respond > Policies > Create Policy Manually.

The Create Policy window contains the following panels:

  • Trigger: Sets the events that trigger the policy, entities that are affected by the policy.
  • Health Rule Scope: Defines the Health Rules that trigger the policy. 
  • Object Scope: Defines the objects that trigger the policy for application and user experience contexts. 
  • Actions: Sets the actions to take when the policy is triggered.

In either panel, you can configure the policy name, enabled status, and whether to batch the actions executed by the policy.

To create policies:
  1. Click Alert & Respond in the menu bar.
  2. Click Policies either in the right panel or the left navigation pane.
  3. Select the context for the policy (specific Application, User Experience, Databases, Servers, or Analytics) from the pulldown menu.
  4. To create a new policy, click the Create Policy (+) button.

You can edit, copy, enable or disable, and delete a policy by clicking the appropriate button.

Configure Policy Triggers

The policy trigger panel defines the events and objects that cause the policy to fire and invoke its actions.

For policy triggers that depend on health violation events, you must create the health rules before you can create a policy that uses them. See Health Rules and Troubleshoot Health Rule Violations.

To configure policy triggers:
  1. Click Create Policy (+ button) or select a policy and click Edit (pencil button).
  2. Enter a name for the policy in the Name field.
  3. To enable the policy, check the Enabled check box. To disable the policy, clear the Enabled check box.
    You can also enable or disable a policy by selecting it in the policy list and clicking the Enable or Disable button.
  4. If you clear the Execute actions in batch check box, the policy fires its actions immediately for every triggering event. If you check this check box, the policy fires its actions once for all the triggering events that occurred in the last minute. See 'Policy Actions in Batch' in Policies.
  5. Select the Trigger panel if it is not already selected.
  6. Check one or more types of events that should trigger the policy. You may need to click the arrow to expose specific events within an event category.
    If you check at least one health rule violation event, you can choose whether any or all health rule violations or only specific health rule violations will trigger the policy.


If your AppDynamics environment includes browser synthetic monitoring, you will see additional other events for Synthetic Availability and Synthetic Performance. See 'Alerting and Synthetics' in Browser Synthetic Monitoring.
You can optionally designate specific custom events to trigger the policy, using the Custom Events panel in the lower right corner. Click the + icon.


Specify the custom event type. Optionally, add particular properties on that event as key/value pairs. For Any, at least one property must exist and match. For All, all properties must exist and match.

Configure Health Rule Violation Triggers

The Health Rule Scope panel determines the scope of the health rule violations that trigger the policy. If you have not created a health rule, you can create one by clicking the Create Health Rule button in this panel. 

To configure the health rule violation triggers:
  1. If you have not already done so, edit the policy to which you want to add Health Rule triggers.
  2. Select the Health Rule Scope panel, then select Any Health Rules if you want the policy triggered by violation of any health rule.
  3. To designate specific health rule violations to trigger the policy, click the + icon, and then choose the health rules from the embedded health rule browser. Click Create Health Rule to create a new health rule as the trigger for this policy.

Configure Object Scope

The Object Scope panel defines the objects the policy is triggered on. The object scope applies only to business transaction performance type health rules and node health type health rules which comprise tiers and nodes

To configure objects to be monitored:
  1. When you have finished selecting the health rule violations that trigger the policy, click the Object Scope panel to select objects to be monitored in case of an event. If you select Any Object, the policy will be triggered by the configured events when they occur on any object in your application.
  2. To restrict the policy to specific objects, select These Specified Objects and then choose the objects.
    For example, the following policy fires when selected events occur on the ECommerce Server tier. You can similarly restrict the objects to specific nodes, business transactions, Ajax Requests, and so forth.

    You can restrict the affected nodes on the node name, on the type of node (such as Java and .NET) on nodes in certain tiers, or on criteria such as meta-info, environment variables, and JVM system environment properties. Meta-info includes key-value pairs for:
    • key: supportsDevMode
    • key: ProcessID
    • key: appdynamics.ip.addresses
    • any key passed to the agent in the appdynamics.agent.node.metainfo system property
    To trigger by Health Rule Violation Events, leave the selection at Any object. Selecting These specified objects means that events occurring within the selected objects, for example, slow transactions, errors, and so forth, trigger the policy.
  3. Click Save.

Configure Policy Actions

The policy actions panel binds an action to the trigger. It defines which actions the policy automatically initiates when the trigger causes the policy to fire.

The actions must be created before you can create a policy that fires them. See Actions and the documentation for individual types of actions (for example, notification actions, remediation actions) for information on creating an action.

To configure policy actions:
  1. If you have not already done so, edit the policy to which you want to add actions. See To Access the Policy Wizard.
  2. Select the Actions panel. 
  3. Click the + icon. The list of existing actions appears. The available actions vary depending on the product area selected for the policy, such as Applications, Servers, Databases and so on.
    You can filter the list by checking the check boxes for the types of actions you want to see.
  4. In the list of actions, select the action that you want this policy to execute and click Select.
    If you do not see an appropriate action for your needs, click Create. For information on creating actions, see Actions. After you have created the action, select it here to assign it to the policy that you are configuring.

  5. Click Save

You can optionally test whether your action will be fired using the Test Action Execution. Ensure that the policy you are testing is enabled.

  • No labels