Overview
This document describes how to add the ConnectWise Asio™ hyperautomation integration to BrightGauge™ and the default metrics that come with it.
Prerequisites
You must first meet the following requirements to connect BrightGauge to ConnectWise Asio hyperautomation:
- You must have ConnectWise SSO enabled.
- ConnectWise Asio must be provisioned to your account with all appropriate entitlements required for integrations with hyperautomation service.
- You must have hyperautomation enabled on your account.
Connect to ConnectWise Asio
To connect to ConnectWise Asio:
- Log in to your BrightGauge account.
- Navigate to Data > Datasources.
- Select ConnectWise Asio.
- Enter the integration Name.
- Click Test Connection.
- After a successful connection, click Save. Dashboards, reports, datasets, and gauges are added to your account after the integration is saved. The sync usually takes 20 to 30 minutes to complete.
Default Resources
BrightGauge provides the following dashboards, gauges, and datasets for the ConnectWise Asio hyperautomation integration.
Default Dashboards
To locate your dashboards, select Dashboards from the top menu bar. Then, click the dashboard name to open the dashboard selection menu.
The Asio integration comes with the Hyperautomation dashboard, below:
Default Gauges
To see your gauges, select Gauges from the top menu bar in BrightGauge.
The Hyperautomation dashboard comes with the following default gauges:
| Gauge |
| Top Workflow |
| Top RPA Bots |
| Workflow Summary (Last 90 Days, Monthly) |
| Workflow Summary (Last 90 Days) |
| Sidekick (Teams Bot) |
| Sidekick Unique Users (Teams Bot) |
| RPA Bots (Last 90 Days, Monthly) |
| RPA Bots (Last 90 Days) |
Field Descriptions
The following fields are available when you build a gauge using the default datasets.
RPA Execution Status
| Field | Description |
| company_id | Company ID that the RPA bot executed against. |
| created_by | Asio user who initiated the RPA bot execution. |
| date_created | The date on which the RPA bot was created. |
| date_updated | The date on which the RPA bot was updated. |
| dp_created_at_dtime_utc | Data created in reporting database (data platform). |
| endpoint_id | Asio agent (RMM) endpoint ID for devices. |
| execution_environment | Execution environment where the bot was executed. |
| execution_id | RPA execution unique identifier. |
| execution_status | Execution final result. |
| executor_user_id | Asio user who initiated the RPA bot execution. |
| id | BrightGauge-generated unique identifier. |
| instance_id | ConnectWise PSA™ (Manage) instance ID from where the RPA bot was triggered. This is empty if triggered by Asio. |
| origin | Where the RPA bot execution was originated. This can be ConnectWise PSA, Asio, or workflow. |
| robot_id | Robot unique identifier. |
| robot_name | Robot name. |
| site_id | Asio site ID against which the RPA bot executed. |
| updated_at_dtimeutc | RPA bot last updated time for execution. |
| updated_by | RPA bot execution last updated by (Asio user). |
RPA Sidekick Data
| Field | Description |
| appname | Message path of the target bot including the name of the bot (e.g., commandbotprod). |
| client_browser | Browser used to run the PSA or Asio instance. This may be empty for Microsoft Teams. |
| event_timestamp | The date and time when the Microsoft Teams bot event took place. |
| id | BrightGauge-generated unique identifier. |
| member | Username for the user using the RPA bot. |
| name | Name of the event performed by the user in Microsoft Teams bot. |
| user_id | User ID for the user running the RPA bot. |
Workflow Execution Status
| Field | Description |
| date_created | Date on which the workflow was created. |
| date_executed | Date on which the workflow was last executed. |
| date_updated | Date on which the workflow was last updated. |
| execution_status | Success or failed execution state in Camunda for a process instance started automatically by the workflow integration service on behalf of the partner. |
| id | BrightGauge-generated unique identifier. |
| instance_id | ID in Camunda for a process instance started automatically by the workflow integration service on behalf of the partner. |
| status_name | Status in workflow management for Business Process Model and Notation (BPMN) generated by the UI. |
| workflow_id | ID in workflow management for BPMN process model generated by the UI. |
| workflow_name | User-friendly name in workflow management for BMPN process model generated by the UI. |
Default Datasets
The following datasets are included:
| RPA Execution Status | Gives details to build analytics around the ConnectWise RPA™ bots' executions. Contains data from the last six months. |
| RPA Sidekick Data | Gives details to build analytics around the events performed by users in the ConnectWise Sidekick™ Teams bot. Contains data from the last six months. |
| Workflow Execution Status | Gives details to build analytics around Workflow executions. Contains data from the last six months. |
Comments
0 comments