Almost all Knowledge Scripts can initiate responsive actions, such as sending e-mail, running an external program, or sending an SNMP trap. You define the conditions under which to perform the action and what action to take. For example, if you want to receive an e-mail when CPU utilization reaches 75% on a server, create a job that checks for a CPU threshold of 75% and specify an e-mail action.
Actions appear in the Actions category of the Knowledge Scripts view. The prefix “UX” identifies actions that AppManager can run on a managed UNIX or Linux computer (for example, Action_UXCommand). AppManager can run all other actions on a managed Windows computer or logical server (including the management server or a proxy server). Note that some actions are application-specific. For example, the Action_IISPauseSite Knowledge Script must run on an IIS server.
Actions for managed Windows resources are Windows actions and actions for managed UNIX or Linux computers are UNIX actions.
The action Knowledge Scripts, such as Action_MAPIMail and Action_Messenger, have built-in severity filtering. Using the Severity Configuration parameters, you can specify the range of severities you want the action to execute.
For more information about action Knowledge Scripts, see the Help.
When monitoring a Windows resource, you can configure a job to initiate a different corrective action depending on when AppManager detects the event condition. To do this, configure more than one Windows action and specify a different action schedule. Building upon the example in the previous section, when CPU utilization exceeds the threshold during business hours, an e-mail action runs; during non-business hours, a page action runs.
Use the AppManager Operator Console to configure the scheduled hours of operation for an action schedule. For more information, see the Operator Console User Guide for AppManager, available on the AppManager Documentation page.
In addition, you can configure an action to run each time AppManager raises an event, only when it creates a duplicate event a specified number of times, or when the event condition no longer exists.
To configure a job to initiate a similar response depending on when AppManager detects the event condition, make a copy of the action Knowledge Script and configure the job to run each action with the corresponding action schedule. For example, if CPU utilization exceeds the threshold during the week, an e-mail action (Action_MapiMail) sends an e-mail notification to the IT operator; if utilization exceeds the threshold on the weekend, an e-mail action (Action_MapiMailOnCallIT) sends an e-mail notification to the on-call IT operator.
When monitoring a UNIX or Linux computer, you can configure a Windows action to run on the management server or a UNIX action to run on the managed UNIX or Linux computer. However, you must configure a UNIX action to run each time AppManager raises an event. In addition, you cannot use action schedules to initiate a different corrective action depending on when AppManager detects the event condition.
You can configure actions for a job when creating a new job, by modifying an existing job, or by modifying a Knowledge Script Group member. After you display the Properties window for the job, the process is similar in all cases. The following procedure assumes you are able to display the Properties window.
To configure a responsive or corrective action for a job:
Display the Properties window for the Knowledge Script job.
Click the Actions tab.
Click New to create a new action and then select an action Knowledge Script from the Action list. If you are monitoring a Windows resource, UNIX actions are not available.
NOTE:To see a list of available actions, click the Actions category in a Knowledge Scripts view.
In the Location column, specify where the action runs:
|
Select... |
To run the action on the... |
|---|---|
|
MS |
Management server. Select this option to initiate a Windows action on the management server. If you are monitoring a UNIX or Linux computer, you must select this option to initiate a Windows action. |
|
MC |
Managed Windows resource (physical computer or logical server). Select this option to initiate a Windows action on the managed Windows resource. If you are monitoring a UNIX or Linux computer, select this option to initiate a UNIX action on the managed computer. |
|
Proxy |
Proxy server. Select this option to initiate a Windows action on a Windows computer with the AppManager agent (netiqmc.exe). This option is not applicable when monitoring UNIX or Linux computers. |
In the Type column, configure an action to run the first time AppManager raises an event (a unique event), after it creates a duplicate child event a specified number of times, or when the event condition no longer exists. Note that you must configure a UNIX action to run the first time AppManager raises an event:
|
Select... |
To run an action... |
|---|---|
|
New event |
The first time AppManager raises an event (a unique event). This is the default. |
|
Repeat Event -n |
When AppManager creates the specified number of duplicate child events. The default value, 1, permits an action each time AppManager creates a new duplicate child event. Specify the number of times that AppManager must create a new duplicate child event to initiate an action. Note that if you enabled event collapsing, increments to the event count of a child event are not the same as a new duplicate child event. For example, if you enabled event collapsing with the default interval of 20 minutes, when AppManager first detects an event condition, it creates a child event. Subsequent events increment the event count until the 20 minute interval has passed. At this point, AppManager can create a new child event. |
|
Event Down |
When the event condition no longer exists. To use this option, check Generate a new event when original event condition no longer exists on the Advanced tab. |
In the Schedule column, select an action schedule to specify the available hours during which the action can run. When monitoring UNIX and Linux computers, action schedules are not applicable.
For information about viewing and configuring the scheduled hours of operation for an action schedule, use the AppManager Operator Console to view the repository preferences. For more information, see the Operator Console User Guide for AppManager, available on the AppManager Documentation page.
(Conditional) To set the properties for an action Knowledge Script, select a Knowledge Script in the Action list and then click Properties.
Most actions require you to set some additional properties. For example, if you select an e-mail action, you need to specify an e-mail recipient. For more information about action Knowledge Scripts and their parameters, see the Help.
Click OK to close the Properties window for the action Knowledge Script.
Click New to configure another action or click OK to start the job.