Configuring Arize for Data Export

Use this guide to configure Arize as a destination for UiPath Data Export. Arize supports OpenTelemetry (OTEL) Trace exports for Maestro and Agent traces.

Prérequis

• An active Arize account.
• Organization Administrator access in UiPath Test Cloud.

Step 1: Gather Arize credentials

Before configuring Data Export, collect the following from your Arize account:

1. Space ID: In Arize, select your workspace name in the top-right corner, then select Copy Space ID.

   

2. Project ID: Open the project you want to send traces to. The Project ID is displayed in the project header next to the project name.

   

3. API Key: Go to Settings > API Keys and copy an active key. If no key exists, select + New API Key to generate one.

   

4. Endpoint URL: Determine the correct endpoint based on your Arize account region:

   Arize region	Endpoint URL
   Non-Europe	https://otlp.arize.com/v1
   Europe	https://otlp.eu-west-1a.arize.com/v1

   Remarque :

   Use your Arize account region, not your UiPath tenant region.

Step 2: Configure Data Export in UiPath

1. In UiPath Test Cloud, go to Admin and select Data Export.

2. Select + Add.

3. Step 1 – Select tenant: Choose the tenant for this export, then select Next.

4. Step 2 – Select data sources: Select Maestro & Agents, then select Next.

5. Step 3 – Configure destination: Select Arize as the connection type and enter the following:

   Champ	Valeur (Value)
   Endpoint URL	The Arize OTLP (OpenTelemetry Protocol) endpoint for your account region (from Step 1).
   Clé API	Your Arize API key (from Step 1).
   Project ID	Enter the Project ID from Arize — not the project display name.
   Space ID	Your Arize Space ID (from Step 1).

6. Step 4 – Review and save: Review the configuration, then select Save.

Result: The new configuration appears in the Data Export table. To verify the setup, trigger any agent run (debug, evaluation, or runtime) or Maestro run. Traces should appear in your Arize project shortly after.

Remarque :

Test Connection is not available for Arize. Verify the integration by triggering an agent or Maestro run after saving the configuration.