Jacada's RPA Monitor provides four different viewing modes to assist you in analyzing and understanding RPA activities: Bots, Services, Methods and Calls.

 

Starting the RPA Monitor

Note: Before you can begin using the RPA Monitor, RPA Services need to be enabled for your account and an RPA Package must be added to the Admin Console.

From the Monitoring section of the Admin Console, click RPA Monitor. The RPA Monitor page opens displaying the Bots view.

 

Viewing Bots in the RPA Monitor

Note: For more information about the RPA Monitor page, see the RPA Monitoring Overview.

The Bots view displays the current version and status of every Bot in the system, along with data about RPA calls executed on that Bot which match the selected time range and filters, as shown above.

Each Bot in the view is presented alongside its key information in a grid. You can click on different columns to change the sort order of the information displayed:

Item Description
Mode The Automation mode selected for the related Bot: either Attended or Unattended . For more information, click here.
Bot Name The names of all Bots in the selected time range.

A 'no-communication' icon will appear at the left side of a Bot that had no Calls for the selected time range or filter.
Package Version The version number of the RPA Package that the designated Bot is currently serving.
Status The current Status of the designated Bot. Bots continuously report their status to Interact. The Bot Status can be:
  • READY. The Bot is available for execution by a Flow.
  • ACQUIRED. The Bot has been called for execution by a Flow and resources have been reserved for it. It is not available for use by another Flow.
  • BUSY. The Bot is currently executing.
  • CLEANUP. The Bot has completed execution and the resources alloted for it are being released.
  • SETUP. The Bot is ACTIVE but cannot be called to execute a Method since it is still setting up.
  • ERROR. An error has been encountered during Bot execution.
  • CLEANUP ERROR. An error has been encountered performing a CLEANUP for the Bot.
  • NOT UPDATED. The Bot is running an outdated Package version and needs to be updated.
  • UPDATING. The Bot is currently being updated to a new version.
  • INACTIVE. The Bot has not reported its status for the required time period. It is not available for execution.
  • DELETED. The Bot was INACTIVE for an extended time period (specified in the RPA configuration) and will need to be reloaded for any future execution.
Uptime The total length of time since the Bot began to report its Status to Interact. If a Bot becomes inactive, the timer stops. The timer will restart after an inactive Bot reports that it is active once again.
Calls The total number of execution calls that the Bot has received for the selected time range or filter.
Errors The total number of erroneous method calls that have been reported by the Bot for the selected time range or filter.
Bot Release Click the Bot release icon to the right of any Bot currently in Acquired status in order to stop it from running and free its resources.

You may want to release a Bot if it appears to be stalled and its assigned timeout period has not yet expired.

 

Applying Quick Filters to the Bots View

When needed (for example, when the Bots list is long) you can create a Quick Filter that shows the activities associated with only a single Bot:



Clicking on a Bot Name (or on the filter icon that appears when you hover over the Bot) adds it to a Quick Filter at the top of the Monitor page and removes all other Bots from the view:

With the filter applied, you can switch between views in the RPA Monitor to see information about all the RPA elements that are related to the selected Bot.

Note: Applying a Quick Filter will update data in all views of the RPA Monitor.

To release an active filter, click on the X at its right side. Adding or releasing a filter does not affect the column sort orders or history selections you have previously made.

 

Revision:

Comments