Each managed MCP, UNIX, and Linux system has an automation mode. The automation mode for each of these managed systems determines the amount of information that is saved to the SP-AMS log for that system. The automation mode also determines whether actions are executed or just written to the SP-AMS log when Operations Sentinel receives a system message that matches a pattern in the active SP-AMS database. You can view the SP-AMS log using Operations Sentinel Log Viewer.
You have individual control over the mode of automation for each managed system. You can specify whether actions are executed, written to a log, or both. Possible automation modes are
Normal
When a pattern in the database is matched, actions defined in the pattern are performed, but are not written to the SP-AMS log.
Trace
When a pattern in the database is matched, actions defined in the pattern are performed and also written to the SP-AMS log. All matched text and pattern match information is also written to this log.
Debug
When a pattern in the database is matched, actions defined in the pattern are not performed, but all actions, matched text, and pattern-matching information are written to the SP-AMS log. Use Debug mode to test which actions SP-AMS performs without actually performing the actions.
Note: The Monitor property for a system must be True for any automation of that system to occur.
To change the automation mode
Under the Managed Objects node, click the desired class (either MCP System or UNIX/Linux System).
In the display pane, click the desired systems.
In the details pane, use the arrow (
) in the Automation Mode property to select one of the following:Normal
Trace
Debug
Any changes you make appear in bold until you save them.
In the details pane, make sure the Monitor property is set to True
Save your changes. The new automation mode immediately affects automation of the system.