Self-Monitoring
Applies To: Opalis 6.3
The self-monitoring feature monitors policies, objects, and database connections. If the self-monitoring feature detects that one of these is not running as expected, it generates event notifications to alert you to intervene and correct the problem.
Self-monitoring runs the OpalisActionServerWatchdog service that starts automatically each time the computer is started. Event notifications are not generated when the OpalisActionServerWatchdog is not running. When the service is restarted, it only sends event notifications for events that did not run as expected since the time the OpalisActionServerWatchdog service restarted.
Monitored Events and Notifications
This feature monitors for and generates event notifications about the following events:
| Event | Description | Notification |
|---|---|---|
Policies have started but are not running. |
When you click Start to launch a policy, this feature monitors how long it takes before the policy starts running. If the policy does not start to run within 60 to 90 seconds, the feature generates an event notification. The event notification is sent once. |
The policy is started, but is not running. |
Policies start, run, and do not restart. |
The self-monitoring feature sends an event notification after 60 to 90 seconds have elapsed. The event notification is sent once. |
The policy is started, but is not running. |
A policy is published two or more times. |
No event notification is generated if at least one of the instances of these policies is running. However, if the first instance of the policy finishes running, and the second instance does not start within 60 to 90 seconds, the self-monitoring feature sends an event notification for the second instance. |
The policy is started, but is not running. |
An action server cannot connect to the datastore. |
If an action server cannot connect to the datastore, the self-monitoring feature generates an event notification. The event notification is sent once. |
The action server cannot connect to the datastore. |
Frequent errors connecting to or writing to the datastore. |
If the self-monitoring feature finds that an action server is encountering difficulties connecting or writing to the datastore, it generates an event notification. This event notification is sent once. |
The action server is experiencing frequent errors while accessing the database. |
An action server has stopped running. |
If the self-monitoring feature finds that an action server has stopped running, it generates an event notification. |
The action server has stopped running. |
The action server is reaching the policy throttling limit. |
If the self-monitoring feature finds that an action server is approaching its policy throttling limit, it generates an event notification. |
The number of policies running on the action server is approaching the maximum number allowed for this action server. |