Automated Responses
A response is an action that is initiated by MOM 2005 when a processing rule match occurs. By using processing rules, you can define an automated response to a detected condition, such as an event, an alert, a performance sample, or a performance threshold. Responses help resolve the issue indicated by the event.
You can define the following automated responses within processing rules:
Table 3.1 Response types and their available options
Response type |
Local Execution |
Server-side Execution |
Alert Dependent |
Timeout Support |
Custom Response Type |
|---|---|---|---|---|---|
Send a notification to a notification group |
No |
Yes |
Yes |
No |
No |
Execute a command or batch file |
Yes |
Yes |
No |
Yes |
Yes |
Send an SNMP trap |
Yes |
Yes |
Yes |
No |
No |
Update state variable |
Yes |
Yes |
No |
No |
No |
Launch a script |
Yes |
Yes |
No |
Yes |
Yes |
Transfer a file |
Yes |
No |
No |
No |
No |
Call a method on a managed code assembly |
Yes |
Yes |
No |
Yes |
Yes |
Local Execution - The response is run on the managed computer.
Server-side Execution - The response runs on the MOM Management Server.
Alert Dependent - The response types are only available when an Alert is generated as part of the rule configuration.
Timeout Support - In order to prevent responses from using up computer resources inappropriately, a timeout setting is available for some response types. This setting allows the Management Pack author to limit the execution time for responses that are not running properly.
Custom Response Type - The execution of server-side responses is regulated by the Disable execution of custom responses on Management Servers global security setting. This setting is enabled by default, and is designed to prevent the execution of custom code as a result of a condition detected on a managed computer. For more information see the MOM 2005 Security Guide.
You can define more than one response for each processing rule match. For example, if an event indicates that an application has stopped, MOM can respond by restarting the application andby paging a network administrator.
In contrast, when you create an alert processing rule, you can assign one response to a number of alerts. For more information about alert processing rules, see the "Alert processing rules" section earlier in this chapter.
All responses, except for the file transfer response, are executed under the context of the configured agent Action Account. File transfers are processed by Background Intelligent Transfer Service (BITS) and run in the Local System context. For more information about the agent Action Account, see the MOM 2005 Security Guide.