You can add tasks and actions to a rule or a policy. Rules are triggered when monitored metric data reaches a determined value or goes beyond an acceptable value range. A triggered rule sends an alert, and any actions or tasks that are specified for that rule are executed.
When actions are part of a policy, the point at which the actions are executed depends upon the severity setting of the action. When actions are associated with a rule, they are executed when that rule is triggered. When actions are associated with a policy, they are assigned a severity state. The actions are executed when a rule with that same severity that is specified for that policy is triggered. Within a policy, each severity state can have an action or set of actions specified for it. For example, you can have rules specified for a policy that have a severity state of Critical. When any of the critical rules are triggered, all of the actions that are specified for the Critical severity state are executed.
Setting actions at a rule level makes the actions more specific by targeting an individual metric. Setting actions at a policy level lets you specify actions so that they are executed to respond to multiple sources. The disadvantage is that the actions may have to be more general.
You can include the same task in multiple rules or policies. Modifying a task in a rule or policy also changes that rule in any other rules or policies that use that task.
You can specify task server actions or Monitor Plug-in actions for your rules and policies. Task server actions are run from the task server, and Monitor Plug-in actions are run from the Monitor Plug-in. Agentless policies can only contain task server actions.
The advantages of using task server tasks are as follows:
You can create jobs from the task server.
You can easily get history information from task server tasks by viewing the task item.
More tokens are available for configuring the tasks than there are for Monitor Plug-in tasks.
More task types available than there are for Monitor Plug-in tasks.
The advantages and disadvantages of using Monitor Plug-in tasks are as follows:
Tasks can be run even if the Notification Server computer is not reachable, which may make Monitor Plug-in tasks very useful for critical tasks.
Not as many task types are available as there are for task server tasks.
Not as many tokens are available for configuring the tasks as there are for task server tasks.
You can only create client tasks.
You cannot create jobs with Monitor Plug-in tasks.
Monitor packs include predefined tasks to meet many of your needs. You can customize tasks further so that the execution of tasks is more useful.
Customizing monitor tasks lets you add additional monitor information to the tasks that are run when a rule is triggered, or as part of a policy. Additionally, you can run tasks independently of any rules or policies. Tasks can be run on demand or on a schedule. With the additional Monitor data, the execution of the tasks is more meaningful.