Audience & purpose

As a Product user with appropriate privileges you will see Robot runners with "Status" widgets on the Robot runners dashboard.

Working with Robot runner Status widgets

Use the following guidelines regarding Robot runner Status widgets.

1. You have "View Robot runners dashboard" privileges and login to Product.
2. The Robot runners dashboard will display Robot runners by Status widgets.
3. In each widget, the system will display the count of Robot runners in each state:
   1. Available
   2. Processing
   3. Disconnected
   4. Deactivated
4. Click any group to display the details of the Robot runners in that group:
   1. Host name
   2. User name
   3. Task name
   4. Start time (for Robot runners currently processing a Robot)

Security

You will only see those Robot runners to which you have access.

Return to top

Audience & purpose

As a Product user with appropriate privileges, you want to see the consolidated view of all Robot runners in different categories (based on their current state) in the Robot runners dashboard.

Working with infrastructure health widgets

Use the following guidelines regarding the infrastructure health widget.

1. You have "View Robot Runners Dashboard" privileges and login to Product.
2. The Robot runners dashboard will display the infrastructure health widget.
3. In this widget, the system will display the following categories:
   • Low Memory
   • Low CPU
   • Low Storage
   • Network Issues (unknown state)
4. Thresholds for the preceding categories will be defined at the system level.
5. Click each category to show the details of the Robot runners in that category.

Security

You will only see Robot runners to which you have access.

Return to top

Audience & purpose

As a Product user with appropriate privileges, you want to see Robot runners with the most failures in the dashboard.

• This will enable you to troubleshoot these failed Robot runners based on their priority.

Troubleshooting Robot runner failures

Use the following guidelines when troubleshooting Robot runner failures.

1. You have "View Robot runners dashboard" privileges and login to Product.
2. The Robot runners dashboard will display the "Robot runners with most failures" widget.
   1. Any Robot execution whose "status" comes back as failed will be counted as a failure.
   2. In the widget, the system will display the top ten Robot runners with the most failures in the system during the last week (by default).
   3. The widget will also capture the number of Robots deployed on that Robot runner during that time showing the failures in percentages (%).
   4. You will be able to specify:
      • The number of Robot runners you want to see in these widgets.
      • The time range (today, this week, this month, custom date) over the last 6 months.
   5. Click each Robot runner to show the details of the Robot that it ran, along with the error details.

Security

You will see an ordered list of Robots based on your access privileges.

Return to top

Audience & purpose

As a Product User with appropriate privileges you will see the most busy and least busy widgets on the Robot runners dashboard. This will enable you to:

• Identify the critical Robot runners in the network to plan DR/Maintenance activities.
• Identify the least used Robot runners to determine where new Robots can be deployed.

Working with the Robot runners dashboard

Use the following guidelines regarding the Robot runners dashboard.

1. You have "View Robot runners dashboard" privileges and login to Product.
2. The Robot runners dashboard will display the "most busy" and "least busy" widgets.
   1. In each widget, the system will display the top ten Robot runners in the system (based on usage).
   2. You will be able to specify:
      • The number of Robot runners you want to see in these widgets.
      • The time range (today, this week, this month, custom date) in the last 6 months.
   3. Click each Robot runner to show the details of the Robots it ran, and how much time it spent on each of those Robots and status.

Security

Users will only see those Robot runners to which they have access.

Return to top

Audience & purpose

As a Product user with appropriate privileges you want to see Robots with a status widget on the Robots dashboard.

• This will give you a consolidated view of all Robots that were deployed in the system.

Working with the Robots Status widget

Use the following guidelines regarding the Robots Status widget.

1. You have "View Robots Dashboard" privileges and login to Product.
2. The Robots dashboard will display Robots by Status widgets.
   • The system will display the count of Robots in each state:
     • In progress
     • Paused
     • Completed
     • Failed
   • "In progress" and "Paused" contain the list of Robots that are currently in progress or paused.
   • The "Completed" and "Failed" group shows the list of Robots that are completed/failed today by default.
3. You can customize the date range to see data for the last six months.
4. Click any group to display the details of the Robots:
   • Host name
   • User name
   • Start time (for bot runners currently processing a bot)
   • End time (for completed ones)
   • Reason for Failure (for failed ones)

Security

You will only see those Robots to which you have access.

Return to top

Audience & purpose

As a Product user with appropriate privileges you want to see the "most busy" and "least busy" widgets on the Robots dashboard.

• This will identify critical Robots in the system so that you can take appropriate measures for access control on these Robots.

Working with the "most busy" and "least busy" Robots widget

Use the following guidelines regarding these widgets.

1. You have "View Robots Dashboard" privileges and login to Product.
2. The Robots dashboard will display the most busy and least busy Robots widgets based on the total processing time of that Robot.
   • In each widget, the system will display the top ten Robots in the system.
   • You will be able to specify:
     • The number of Robots you want to see in these widgets.
     • The time range (today, this week, this month, custom date) over the last six months.
3. Clicking each bot should show:
   • Details of its executions
   • Where it was deployed
   • Start time
   • End time
   • Status

Security

You will only see those Robots to which you have access.

Return to top

Audience & purpose

The Player monitors the health of the infrastructure. It will report the operational data for every task that is deployed so that it can be viewed in operational metrics:

• Robot start time
• Robot running
• Robot end time
• Client login time

Starting a task execution

Use the following guidelines regarding the start of a task execution.

Robot runner will send the following data to Product when a task execution starts.

1. This data needs to be captured for all tasks even if analytics is not enabled for a task.
   1. Machine ID\HostName, IP Address
   2. Unique Robot ID (GUID), Robot Name, Robot Type, Robot Path
   3. User ID (a user that is logged into an Product Enterprise Client) plus Windows User ID
   4. Product User ID (the one who scheduled and runs the Robot from Product)
2. Already sending with activity feedback:
   1. Current Date and Time
   2. Automation name
   3. Unique Run ID/Session ID
   4. Started On
   5. Task ID
   6. Task Name
   7. Total Lines
   8. Current Line
   9. Action Name of the line
   10. Command
   11. Progress
   12. Task File Path
3. New data to send from the Client service
   1. CPU Usage
   2. Memory Usage
   3. Disk Usage/Space (on the Robot Runner machine :Real or Virtual)
   4. Available CPU (in %)
   5. Available Memory (in %)
   6. Available Storage (in %)

RobotRunner will send the following data to Product when a task execution starts.

1. This data needs to be captured for all tasks even if analytics is not enabled for a task.
   1. Start date and Time
   2. Machine ID, HostName, IP Address, Machine Type (VM, Real, VDI), Model, Number of CPUs, Memory, Storage, Processor
   3. Unique Robot ID (GUID), Robot Name, Robot Type, Robot Path
   4. User ID (user that logged into AAE Client) + Windows User ID
   5. Product User ID (one who scheduled/runs the Robot from Product)

During execution

Robot runner will send health blips during a task in progress.

1. It will share the following data with Product in health blips.
   • Action name of the line
   • Automation name
   • Available CPU (%)
   • Available memory (%)
   • Available storage (%)
   • Command
   • CPU usage
   • Current date and time
   • Current line
   • Disk usage/space (on the Robot runner machine – Real or Virtual)
   • Host name
   • Memory usage
   • Progress
   • Started on
   • Task file path
   • Task ID
   • Task name
   • Total lines
   • Unique Run ID/Session ID
2. Health blips will keep coming even if the Robot is stuck and the Player is responsive.
3. The periodic frequency of blips will be configurable. Default: 500 ms
4. The frequency of logging this health blip can be configured at each Robot level (during a Robot's design/schedule time and filtered server-side).

End of execution

Robot runner will send the following data to Product when the task execution ends:

1. Finished time
2. Run ID
3. Run status
4. Status
5. Task ID

Following up

Further considerations regarding the Player and infra health:

1. Date format will be in the international date format ISO 8601, for example: 2017-08-31 (YYYY-MM-DD).
2. Existing behavior with Robot insight and the Player remains the same as in versions 10.x.
3. Product will store all of this operational data reported by the Player.
   • Model: Send from the Client at Login time.
   • Processor: Send from the Client at Login time.
   • Number of CPU Cores: Send from the Client at Login\Auto-login time.
   • Total HDD (App Path, Deployment Path, Temp Path): Send from the Client at Login\Auto login time.
   • Total Memory: Send from the Client at Login\Auto login time.
   • Used CPU: Send from the Client service during task execution.
   • Used Memory: Send from the Client service during task execution.
   • Used HDD (App Path, Deployment Path, Temp Path): Send from the Client service during task execution.

Return to top

Audience & purpose

As a Product user you want to see important, critical alerts on the Dashboard so that you can quickly react and remedy them.

Alert Activities

Use the following guidelines regarding Dashboard Alerts.

1. You have "View Home Dashboard" privileges and login to Product.
2. The "Home" Dashboard will display the "Alerts" widget. See the following screenshot.

   

3. Alerts will be categorized into three groups based on priority:
   1. Critical
   2. High
   3. Medium
4. An Alert can move from one group to another based on the time.
   • This will be specific to each type of Alert.
     • For example, an Alert to inform of a license expiry may initially have a Medium priority (expiring in 60 days).
     • This will move into "High" priority if it is expiring in 30 days. and
     • Later it will be moved to "Critical" priority if it is expiring in 10 days or less.
   • A particular alert will disappear from the widget as soon as a remedy action has been taken by you.
   • For example:
     • If a new license file is added to the system that does not expire in 60 days, an Alert will be described as follows:
       1. Date → Date the Alert occurred.
       2. Severity → Severity of the Alert: Critical/High/Medium
       3. Category → Product/CV/DB/Auto Login/License
       4. Description→ Description of the Alert.
       5. Details → Details of the Alert.
   • You will be able to search/filter the Alerts based on Date, Priority, and Type.

Alert examples

Here is a list of Alerts.

"License expiration"

▸ Show the "Medium" Alert when the license is expiring in 60 days.

▸ The severity will change to "High" if it is expiring in 30 days, and change to "Critical" when it is expiring in less than 15 days.

▸ If a user updates the license, then the Alert will disappear from here (if it is not expiring in 60 days or less anymore).

▸ If a user updates the license, then the Alert will disappear from here (if it is not expiring in 60 days or less anymore).

▸ An Admin only can see this message

"Auto login failures" (Machine auto login while executing a Robot)

▸ Capture all "Auto login" failures and show them with "Critical" severity.

▸ As and when a user updates their Auto login password, or Auto login is working for that user, then all the Alerts for that user will disappear.

▸ An Admin sees all errors. A user only sees his error.

"Product server thresholds breached for memory/CPU/hard disk"

▸ Threshold values will be captured in the Control room.

▸ As and when these thresholds are breached, it will log an Alert.

▸ If more than one Product server is there, capture the information for all Products.

▸ An Admin only can see this message.

"DB running of out of space (only 10% left)"

▸ An Admin only can see this message.

Security

Users will only see Alerts that they are entitled to view.

Return to top