View logs and details to record user activities.
Audit Log displays a read-only table of records of actions performed by users. These log records are searchable and exportable. Audit logs include both Successful and Unsuccessful actions attempted.
The following Audit log actions are enabled:
- Time filter
- Users select from preset time filters or configure a custom time filter for log entries to view. The default time filter setting is Last 24 hours.
- Search the records. Select additional search filter criteria from the
drop-down menu. Tip: To search the exact phrase, enclose the search phrase within double quotes (for example, "Juan-Finance-564").
- Export checked items to CSV
- Export the data to a CSV file based on filters and or selections.
- Refresh and view the updated status.
- Customize columns
- Show or hide specific columns.
- To view details of a table entry, mouse over the entry to expand and click Audit details.
Audit log table
|Status||Shows action status.|
|Time||Shows the date and time of the action performed.|
Shows the type of action performed.
|Item Name||Shows the entity on which action was performed.|
|Event Started By||Shows the user that performed the action.|
|Source Device||Shows the device or machine name or IP address that was used to perform the action.|
|Source||Shows the component: Control Room, Enterprise Client or API, from where the action originated or was performed.|
|Request ID||Shows the unique identity number assigned to a specific set of user actions.|
Understanding audit logs
|Audit log entry||Success||Failure|
|Create automation||Bot was sent to the control room and was successfully compiled.||Check if the Control Room is up and running.|
|Bot Sent To Device||Control Room deployed the bot successfully on the specified device.||Possible reasons for failure entry include:
|Run bot Deployed||The bot has started on the specified device.||Possible reasons for failure entry include:
|Run bot finished||Bot execution completed successfully.||Possible reasons for failure entry include:
|Bot Runner Session Continued||Control Room deploys the TaskBots in a sequence for the same RDP session.||Possible reasons for failure entry include:|
|Bot Runner Session Released||When a task successfully completes the execution.||Possible reasons for failure entry include:|
|Download file||Downloading to the Control Room.||Possible reasons for failure entry include:|
|Upload file||Uploading a file to the Control Room.||Possible reasons for failure entry include:|
|Bot Runner Session||Control Room gets the RDP session of Bot Runner machine.||Possible reasons for failure entry include:|
Automation Anywhere Robotic Interface (AARI) Audit logs
|Audit log entry||Success|
|AARI Human Task||
|AARI Bot Task||When the process launched a bot task|
|AARI Bot Setup||
|Process Scheduler||When the scheduler configuration is modified|