Observability for Prompt Flow with Opik

Prompt Flow enables tracing through Prompt Flow APIs and uses OpenTelemetry export settings for outbound telemetry.

When this guide applies

Use this when your Prompt Flow project already uses Prompt Flow tracing and you want its telemetry exported into Opik.

Opik OTLP endpoint modes

For full endpoint/header details, see Opik OpenTelemetry overview.

$
export OTEL_EXPORTER_OTLP_ENDPOINT=https://www.comet.com/opik/api/v1/private/otel
$
export OTEL_EXPORTER_OTLP_HEADERS='Authorization=<your-api-key>,Comet-Workspace=<your-workspace>,projectName=<your-project-name>'

Example (Prompt Flow tracing API)

Intent: Enable Prompt Flow tracing and export telemetry through your configured OTLP endpoint.

Applies when: You use Prompt Flow’s native tracing API and want those traces exported via your OTEL settings.

Required inputs:

• Prompt Flow tracing enabled in code
• OTEL endpoint/header env vars for your Opik mode

Optional inputs:

• service/resource metadata
• additional OTel collector routing or enrichment

Minimal valid setup:

1
from promptflow.tracing import start_trace
2
3
start_trace()
4
5
# Run prompt flow pipeline as usual.

Validation

1. Run a flow with start_trace() enabled.
2. Confirm telemetry export calls are made to your configured OTLP endpoint.
3. Verify trace records appear in the expected Opik project.

Source references

• Prompt Flow tracing docs
• Opik OpenTelemetry overview