On this page:
There are two ways to configure policies:
If all you want to do is set up a very simple policy that sends an email message to a recipient when a health rule violation event occurs, you can click the Policy Setup Wizard button or the Policy Setup Wizard link.
To create a simple notification policy, you must set up an SMTP server (see Enable an Email Server) and supply an email address. The policy is then created:
You can modify the policy later the same way you modify a policy that was created manually.
The Manual Policy Wizard contains two panels:
In either panel you can configure the policy name, enabled status, and whether to batch the actions executed by the policy.
You can also copy, enable or disable a policy by clicking the appropriate button.
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, the health rules must be created before you can create a policy on them. See Health Rules and Troubleshoot Health Rule Violations.
Check the type of event(s) 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 (that is, all) health rule violation or only specific health rule violations will trigger the policy.
When you have finished selecting the events that trigger the policy, click any object to configure which objects to monitor for those events to trigger the policy.
If you select Any Object, the policy will be triggered by the configured events when they occur on any object in your application.
To restrict the policy to specific objects, select Any of these specified objects and then choose the objects.
For example, the following policy fires when selected events occur on the 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 (Java, .NET, etc) 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:
To trigger by Health Rule Violation Events, leave the selection at Any object. Selecting Any of these specified objects means that only non-health rule events - slow transactions, errors, and so forth - will trigger the policy.
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 (notification actions, remediation actions, etc.) for information on creating an action.
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 Action. 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.
You can optionally test whether your action will be fired using the event simulation tool before you enable the policy in production.