Task management
We can be notified about decisions that are made by autonomic managers. Notifications can represent either planned or unplanned events.
- Planned events
- Planned events are events for which the runtime environment has an action plan. For example, we might have a health policy defined that has an average response time that is breaching its configured limit, which might trigger an increased footprint of a dynamic cluster. If the product is operating in automatic mode, then the action plan runs, and we can view a notification of the action that was taken. In supervised mode, we can view and approve the action plan. The interaction modes can vary in the configuration. A mix of automatic and supervised mode activities by dynamic clusters and health policies can exist, for example.
- Unplanned events
- If an event occurs and it is not assigned to an action plan, then we can be notified that something unexpected has happened. After we receive the notification, develop a plan to correct the situation, if it is a valid issue.
- Runtime tasks
- A runtime task is generated when an event occurs. Runtime tasks provide information from which we can accept, deny or close the recommended action plan. Tasks that have taken action or expired tasks stay in the runtime task list for 24 hours by default. We can change this default by setting a cell level custom property.
Runtime tasks reside in the deployment manager memory, and are logged in...
<was_root>/profiles/<Dmgr_profile>/tmsStorage
When the deployment manager is restarted, the deployment manager reads the runtime task entries in the tmsStorage log.
- Event logging
- We can enable logging for events.
- Notifications
- We can have email notifications sent to specified users when runtime tasks occur.
Related:
Task management service event logger Monitor Intelligent Management operations Manage runtime tasks Define email notification Intelligent Management: runtime task custom properties