The status of the tasks that were recently initiated from VMware vRealize Operations Cloudappears in the Recent Task list. You can determine whether a task is finished, still in process, or failed.
How Recent Tasks Work
The Recent Tasks page reports on logged task events, and the log entries appear in the messages area so that you can troubleshoot failed tasks.
Where You View Recent Tasks
From the left menu, select Recent Tasks., then click
Recent Task Options
Review the information in the task list to determine if a task is completed or if you must troubleshoot a failed task. To see the details about a task, select the task in the list and review the associated objects and task messages.
Exports the selected task to an XML file.
The exported information, which includes the messages, is useful when you are troubleshooting a problem.
Determines how long the recent task data is retained in your system.
Set the number of days that vRealize Operations Cloud keeps the data, after which it is purged from the system. The default value is 90 days.
|Status drop-down menu||
Filters the list based on the status value.
Filters the list based on the selected column and the provided values. You can filter the tasks based on the following criteria.
|Filter (Object Name)||
Limits the tasks in the list to those that match the entered string.
The search is based on a partial entry. For example, if you enter vm, objects such as vm001 and acctvm_east are included.
Name of the task.
For example, Set CPU Count for VM.
State of the task.
Possible states include the following values:
Date and time when the task started.
Date and time when the task finished.
A completed date does not appear if the task failed or if the maximum timeout is reached.
Indicates whether the action in the task list is automated, indicated by Yes or No.
Object on which the task was started.
Type of object on which the task was started.
The UUID or the name of the event that triggered the action automatically. when an event is triggered that is associated to the recommendation, it triggers the action without the user intervention.
For example, you can automate Alert recommendations that have an associated action. Automation is disabled by default. You configure automation in the Override Alert / Symptom Definitions area of a policy when you create or edit the policy in .
An administrator who has the Automation role has permission to automate actions in the Override Alert / Symptom Definitions area of the policy workspace.
Authentication source that the user who started the task used when accessing vRealize Operations Cloud.
Name of the user who initiated the task. This column displays the automationAdmin user account for automated actions that are triggered by alerts.
ID generated when the task, which included one or more actions, was started.
The task ID is unique for the task for each adapter. If a task includes tasks that ran using two adapters, you see two task IDs.
If the task is a delete snapshot action, two task IDs are generated. One ID is for the retrieve snapshots based on date task, and the other ID is for the delete selected snapshots task.
The Associated Objects are the objects on which the selected task ran.
Detailed list of objects that are included in the task selected in the task list.
If the task ran on only one object, the list includes one object. If the task ran on multiple objects, each object is listed on a separate row.
Type of object for each object name.
Current state of the task.
The Messages are the log of the task as it ran. If the task does not finish successfully, use the logs to identify problems.
|Severity drop-down menu||
Limits the messages based on the Severity value.
Limits the message in the list to those that match the entered string.
The search is based on a partial entry. For example, if you enter id, then messages that contain Task ID and the phrase did not complete are included.
Message level in the logs.
The severity includes the following values:
Date and time the entry was added to the log.
Text of the log entry.
Use the information in the message to determine why a task failed, and to begin to troubleshoot and resolve the failure.
The messages appear with the most recent entry at the top of the list if you do not sort the columns.