- Getting started
- Data security and compliance
- Organizations
- Authentication and security
- Licensing
- About licensing
- Unified Pricing: Licensing plan framework
- Activating your Enterprise license
- Migrate from Test Suite to Test Cloud
- License migration
- Assigning licenses to tenants
- Assigning user licenses
- Deallocating user licenses
- Monitoring license allocation
- License overallocation
- Licensing notifications
- User license management
- Tenants and services
- Accounts and roles
- AI Trust Layer
- External applications
- Notifications
- Logging
- Data Export
- Testing in your organization
- Troubleshooting
- Migrating to Test Cloud
Test Cloud admin guide
Data Export is a unified interface in the Admin Portal that lets organization administrators create, manage, and monitor export configurations for UiPath platform data.
To access Data Export, navigate to your organization, select the Admin tab, and then select the Data Export card.
Overview
With Data Export, you can:
- Create export configurations for Orchestrator events, tenant audit logs, Maestro traces, and agent traces.
- Route data to external destinations such as Azure Event Hub, AWS Simple Queue Service (SQS), Arize, Databricks, and other observability platforms.
- Monitor the health of export configuration and troubleshoot delivery issues.
- Manage all export pipelines from a single interface.
Prerequisites
- You must be an Organization Administrator to access and configure Data Export.
- Tenants without Insights enabled are not available for export configuration.
Data Export table
The Data Export page lists all export configurations for your organization. You can search the list and filter it by tenant. Select + Add to create a new configuration, or use the three-dot menu on a row to edit or delete it.
Each configuration row shows the following columns:
| Column | Description |
|---|---|
| Created At | The date and time the configuration was created. |
| Tenants | The tenant the configuration applies to. |
| Data Sources | The data sources included in the export. |
| Data Type | The format of the exported data: JSON for event-based exports, or OTEL Trace for OpenTelemetry (OTEL) trace-based exports. |
| Destination | The destination system where data is sent. |
| Status | Status of the connection. Only available for Databricks, AWS SQS, and Azure Event Hub. |
Supported data sources and destinations
| Data Source | Scope | Data Type | Supported Destinations |
|---|---|---|---|
| Orchestrator Events | Tenant | JSON | Azure Event Hub, AWS SQS |
| Audit Logs | Tenant | JSON | Azure Event Hub, AWS SQS |
| Maestro Events | Tenant | JSON | Azure Event Hub, AWS SQS |
| Agent and Maestro Traces | Tenant | OTEL Trace | Databricks, Arize, or OTLP (OpenTelemetry Protocol) Endpoint |
Creating an export configuration
To create an export configuration, select + Add from the Data Export page, then complete the four wizard steps.
Step 1: Select tenant
-
Select the tenant or tenants for this export configuration.
Each tenant supports a maximum of two export configurations: one event-based (JSON) and one OTEL trace-based. If a tenant has reached this limit or already an existing configuration for that data source, it will appear greyed out.
-
Select Next.
Step 2: Select data sources
-
Select the data sources to include in this export.
All selected data sources must share the same data type. You cannot combine JSON event-based sources with OTEL trace sources in a single configuration.
-
Select Next.
Step 3: Configure destination
-
Configure the destination for your export.
The available options depend on the data type of the selected sources.
For event-based (JSON) destinations:
Destination Required Parameters Azure Event Hub Connection String AWS SQS Access Key ID, Secret Access Key, Queue URL, Region For OTEL Trace destinations, choose either Integration Service Connection or Endpoint URL:
Destination Required Parameters Databricks (Integration Service) Integration Service Connection Arize API Key, Endpoint URL, Headers (pre-populated), Custom Headers OTLP Endpoint API Key, Endpoint URL, Custom Headers Note:All custom header values are encrypted at rest.
To validate connectivity before saving, select Test Connection if available:
- Azure Event Hub and AWS SQS: Test Connection sends a test event to the destination.
- Databricks (Integration Service): Test Connection validates the integration service connection only.
- Test Connection is not available for Arize and OTLP Endpoint destinations.
-
Select Next.
Step 4: Review and save
- Review the configuration details.
- Select Save to create the export configuration. Save is active only when all required fields are filled.
Result:
The new export configuration appears in the Data Export table. The Status column reflects whether data is being delivered successfully.
Managing export configurations
Editing a configuration
- On the Data Export page, locate the configuration you want to update.
- Select the three-dot menu on the configuration row, then select Edit.
- Update the configuration details and select Save.
Result: The Data Export table reflects the updated configuration details.
Deleting a configuration
- On the Data Export page, locate the configuration you want to remove.
- Select the three-dot menu on the configuration row, then select Delete.
- Confirm the deletion.
Result: The configuration is removed from the Data Export table.
Routing
Exports are sent through a single static outbound IP address. Add this IP to the allowlist in your destination's firewall rules. For the full list of outbound IP ranges by region, see Configuring the firewall for Test Cloud.
Related documentation
- Overview
- Prerequisites
- Data Export table
- Supported data sources and destinations
- Creating an export configuration
- Step 1: Select tenant
- Step 2: Select data sources
- Step 3: Configure destination
- Step 4: Review and save
- Managing export configurations
- Editing a configuration
- Deleting a configuration
- Routing
- Related documentation