When Operations Sentinel starts monitoring a system, SP-AMS generates and processes an automation initialization message before it processes the first message from the managed system. Because the message is generated internally, it is not displayed in any console window.
Note: Logging of host messages by Operations Sentinel can occur without a true connection to a host system and the start of logging does not in itself cause the generation of the automation initialization message.In addition, an Event Services API client can connect to the Operations Sentinel server without affecting SP-AMS or causing the generation of an automation initialization message.
Purpose of Automation Initialization
The purpose of the automation initialization message is to prepare Operations Sentinel and the host for monitoring. The initialization message is processed by SP‑AMS as if it originated from the managed system. Therefore, you can create patterns to match the message and perform initialization actions for each system you want to monitor.
ACTIVATE or DEACTIVATE Action during Initialization
If the automation initialization message is generated when a database is currently active, and Operations Sentinel starts monitoring a previously unmanaged host, any ACTIVATE or DEACTIVATE action in the pattern matching the initialization message is executed.
If the automation initialization message is generated when a database is being activated, and the pattern that matches the message includes an ACTIVATE or DEACTIVATE action, SP-AMS produces a warning message and does not execute the action. However, if the ACTIVATE or DEACTIVATE action is delayed with a WAIT clause, it is executed after the original activation is completed.
Text of Automation Initialization Message
The text of the automation initialization message is as follows:
Single Point AMS automation started using database db-name for system host-id
where:
db-name
identifies the database you are using.
host-id
identifies the system you are monitoring.