- 入门指南
- 数据安全性与合规性
- 组织
- 身份验证和安全性
- 许可
- 租户和服务
- 帐户和角色
- Ai Trust Layer
- 外部应用程序
- 通知
- 日志记录
- Data Export
- About Data Export
- Data Export data model
- Configuring Azure Event Hub
- Configuring AWS SQS
- Configuring Arize
- Configuring Databricks
- Configuring an OpenTelemetry Collector
- 在您的组织中进行测试
- 故障排除
- 迁移到 Test Cloud
Test Cloud 管理员指南
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.
先决条件
- 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:
字段 描述 API 密钥 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:
- 选择“添加标头” 。
- Enter the Header Name and Header Value.
- Repeat for each header required. Remove a header using the delete icon.
备注：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.