Admin Console
Admin Console is a tenant-level management interface within Robility Manager that enables tenant admins and RPA developers to manage machines hosting the Runner. It provides access to Runner machine resources associated with automation projects through dedicated resource pages.
Users can perform machine management operations without requiring direct access to the target machines. A secure, single connection between Robility Manager and the Runner enables users to remotely send supported commands, monitor machine health and Runner status, access execution and diagnostic logs, and perform operational management tasks from a centralized interface. This capability is supported for Unattended Runner machines and is not applicable to Machine Templates. It improves operational visibility, simplifies troubleshooting, and streamlines the administration of unattended automation environments.
Key Features
- Centralized Machine Management – Monitor and manage all machines running the Robility Unattended Runner from a single interface within Robility Manager.
- Remote Maintenance – Perform administrative actions such as restarting machines, repairing the Runner, resetting the Runner, and disconnecting the Runner remotely.
- System Health Monitoring – Monitor machine health and resource utilization, including CPU, memory, and disk usage, in real time.
- Process Management – View active processes and terminate unwanted or unresponsive applications directly from the Admin Console.
- Log Management – Configure, download, and manage Runner logs to support troubleshooting, diagnostics, and issue resolution.
- Audit Visibility – Track administrative actions and command execution history through the Admin Audit Analytics Dashboard, ensuring enhanced monitoring, accountability, and operational transparency.
Limitations
- The Admin Console is available only to users with the Tenant role. Users with other roles cannot access the Admin Console.
- The Admin Console is accessed from the Resources page for each individual machine.
Prerequisites
Before using the Admin Console for a machine, ensure the following prerequisites are met:
-
The Runner is connected using a Manager Connection Key and is running the latest supported Runner version.
If the Runner is running an outdated version, the Admin Console may not function correctly. -
The Runner machine is online and reachable.
The machine must be powered on, connected to the network, and actively communicating with Robility Manager. If the machine is offline, disconnected from the network, or otherwise unreachable, the Admin Console cannot send or execute administrative commands.
Important: If the Runner is connected using an older Runner version, upgrade the Runner to the latest supported version and reconnect it using a Manager Connection Key.
Once these prerequisites are met, Robility Manager can securely communicate with and manage the connected Runner machine through the Admin Console.
Runner Status
The Runner Status indicates whether the selected Runner is currently connected and available to receive commands.
| Status | Description |
|---|---|
| Online | The Runner is connected to Robility Manager and is available to receive and execute commands. |
| Offline | The Runner is not connected to Robility Manager and cannot receive commands. |
Command Categories
The Admin Console organizes commands into categories based on their function, helping administrators quickly locate and perform the required administrative actions.
| Category | Command | Description |
|---|---|---|
| Logs | Download Logs | Downloads Runner logs for a selected date range of up to seven days. The downloaded log file is saved to the local machine from which you are accessing Robility Manager, not to the Runner machine. |
| Maintenance | Restart Machine | Restarts the selected machine remotely. This is useful when the machine is unresponsive or requires a restart after configuration changes. The Runner automatically reconnects to the Admin Console once the machine is back online. |
| Repair Runner | Repairs the Runner installation to resolve issues and restore Runner functionality. | |
| Reset Runner | Resets the Runner. After resetting, the Runner must be manually reconnected using a Manager Connection Key. | |
| Disconnect Runner | Disconnects the Runner from the manager. The Runner must be manually reconnected using a Manager Connection Key to receive commands again. | |
| System Monitoring | Memory Usage | Displays the current memory usage of the machine. |
| CPU Usage | Displays the current CPU usage to help identify performance issues affecting automation runs. | |
| Disk Usage | Displays used and available disk space to help identify low-storage issues before they impact automation. | |
| Running Processes | Lists all active processes on the machine. Processes can be terminated using the Kill option after confirmation. | |
| Top Processes | Displays the top five processes consuming the most system resources. These processes can be terminated using the Kill option after confirmation. |
Runner Log Level
| Command | Description |
|---|---|
| Activity Log | Controls the level of logs captured in the Activity Log. Available levels are Error, Trace, Info, and Debug. |
| Product Log | Controls the level of logs captured in the Product Log using Error, Trace, Info, and Debug log levels. |
Log Maintenance
| Command | Description |
|---|---|
| Clear Runner Logs | Deletes Runner log files from the machine to free up storage space. This action is permanent, so download any required logs before clearing them. |
Notes
- System Monitoring: Memory Usage, CPU Usage, and Disk Usage display results in the Live Console panel instead of opening separate reports.
- Maintenance: After using Reset Runner or Disconnect Runner, reconnect the Runner using the Manager Connection Key.
Important
a. Kill Running Applications
Warning: Terminating a process can impact running automations, active applications, or unsaved data on the target machine. Use the Kill option with caution and verify the selected process before proceeding. Once a process is terminated, any associated tasks may fail, applications may close unexpectedly, and unsaved changes may be lost.
The Running Processes and Top Processes commands allow you to terminate applications using the Kill option. A confirmation prompt is displayed before termination to ensure you review and confirm the action before the process is stopped.
b. Log Level Synchronization
Changes to Activity Log or Product Log levels in Robility Manager are automatically synchronized with the Runner.
Command Execution and Viewing Results
After sending a command from the Admin Console, the result is displayed automatically in the Live Console panel. The panel shows the response returned by the executed command.
Live Console
The Live Console is a real-time activity log that displays timestamped command execution details and responses from the connected Runner machine. It allows you to monitor command progress, verify results, and identify errors without requiring direct access to the machine.
Options
- Copy — Copies the console log to the clipboard for sharing or troubleshooting.
- Clear — Removes all entries from the console view.
Admin Audit Analytics Dashboard
The Admin Audit Analytics Dashboard provides a centralized view of all commands executed through the Admin Console across all machines.
Administrators can use this dashboard to monitor command activity, review execution status, and track administrative actions performed by users for auditing and troubleshooting purposes.
Filters
Use the following filters to narrow down audit results:
| Filter | Description |
|---|---|
| Search | Searches audit records based on text input, such as a machine name, user, or command. |
| From Date / To Date | Filters results within a specific date range. |
| Event Type | Filters results by command type, such as Restart Machine. |
| Status | Filters results based on command execution status. |
Click Apply to refresh the audit results based on the selected filters.
Status
| Status | Description |
|---|---|
| All | Displays all audit records regardless of status. |
| Success | The command was completed successfully. |
| Pending | The command was sent but the machine has not responded yet. |
| Failed | The command was not completed successfully. |
Audit Events Grid
The Audit Events Grid provides detailed information about commands executed through the Admin Console. Administrators can use the grid to review individual command executions.