- 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
- About Data Export
- Data Export data model
- Configuring Azure Event Hub
- Configuring AWS SQS
- Configuring Arize
- Configuring Databricks
- Configuring an OpenTelemetry Collector
- Testing in your organization
- Troubleshooting
- Migrating to Test Cloud
Test Cloud admin guide
Use this guide to configure a generic OpenTelemetry (OTEL) Collector as a destination for UiPath Data Export. This option works with any OTEL-compatible observability platform that accepts OTLP (OpenTelemetry Protocol) over HTTP, including Langsmith, Langfuse, and MLFlow.
Prerequisites
- An OTLP-compatible HTTP endpoint.
- An API key or other authentication credentials required by your collector (if applicable).
- Organization Administrator access in UiPath Test Cloud.
Configuring an OpenTelemetry Collector
-
In UiPath Test Cloud, go to Admin and select Data Export.
-
Select + Add.
-
Step 1 – Select tenant: Choose the tenant for this export, then select Next.
-
Step 2 – Select data sources: Select Maestro & Agents, then select Next.
-
Step 3 – Configure destination: Select OpenTelemetry Collector as the connection type and enter the following:
Field Description API Key The API key required by your OTEL collector, if applicable. Endpoint URL The OTLP HTTP endpoint URL (for example, https://api.example.com).Optionally, add Custom Headers to pass vendor-specific metadata:
- Select Add Header.
- Enter the Header Name and Header Value.
- Repeat for each header required. Remove a header using the delete icon.
Note:Custom header values are encrypted at rest. Test Connection is not available for the OpenTelemetry Collector destination.
-
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, then confirm that traces appear in your observability platform.