[Question]: Opik TraceId Retrieval from OpenTelemetry (Go)

[saravanan1102]

What component(s) are affected?

• Opik Python SDK
• Opik Typescript SDK
• Opik Agent Optimizer SDK
• Opik UI
• Opik Server
• Documentation

Opik version

• Opik version: x.x.x

Describe the problem

Is it possible to get the Opik traceId from OpenTelemetry?

I’m using a Golang service, and since Opik does not provide a native Go SDK, I’m exporting traces using OpenTelemetry.

I’m able to export the traces successfully, but is there a way to retrieve the actual Opik traceId?

Reproduction steps and code snippets

No response

Error logs or stack trace

No response

Healthcheck results

No response

[ollieagent]

Thank you for your question. Currently, there is no public API in Opik to directly map an OpenTelemetry traceId to an Opik traceId. The internal system does map OpenTelemetry trace IDs to Opik UUIDs using a deterministic algorithm, but this mapping is not exposed externally.

If you are exporting traces using OpenTelemetry from a Go service, these traces can be viewed in the Opik UI, but there is no direct way to retrieve the Opik traceId using an OpenTelemetry traceId through an API.

If exposing such a feature is crucial for your use case, I recommend suggesting it as a feature request. This would require architectural changes and would need to be considered by the maintainers of the project. Let me know if you have any further questions or need additional assistance!

---

_{This is an automated response. Responses may be inaccurate—please verify important details.
trace: 019c8fee-850a-7f11-bcf8-39b3cfd9e5a4}