Simulation Traces

Link OTLP traces to simulation results so the trace flamegraph appears alongside the simulation evaluation in the Bluejay dashboard.

How It Works

Instrument your agent to export OTLP traces to Bluejay — see Sending Traces to Bluejay.
Collect trace IDs generated during the simulation call.
Extract the simulation_result_id — Bluejay injects X-Simulation-Result-Id into every simulation call via SIP headers, WebSocket connect messages, or LiveKit participant attributes.
POST to /v1/update-simulation-result with both simulation_result_id and trace_ids after the call ends.

import httpx

async def link_traces_to_simulation(simulation_result_id, trace_ids, api_key):
    async with httpx.AsyncClient(timeout=10) as client:
        await client.post(
            "https://api.getbluejay.ai/v1/update-simulation-result",
            json={
                "simulation_result_id": simulation_result_id,
                "trace_ids": trace_ids,
            },
            headers={"X-API-Key": api_key},
        )

Call tracer_provider.force_flush() before POSTing trace IDs. If you POST before the spans have been exported, the traces may not be available in Bluejay yet.

The /v1/update-simulation-result endpoint also accepts tool_calls, events, and metadata alongside trace_ids. See Simulation Tool Calls for details.

Update Simulation Result

Full endpoint reference.

Simulation Tool Calls

Enrich simulation results with tool call data.

LiveKit Traces

LiveKit-specific trace linking guide.

Sending Traces to Bluejay

OTLP setup and instrumentation.

Getting Started

Key Concepts

Test

Monitor

Integrations

How It Works

Update Simulation Result

Simulation Tool Calls

LiveKit Traces

Sending Traces to Bluejay

​How It Works

Update Simulation Result

Simulation Tool Calls

LiveKit Traces

Sending Traces to Bluejay

How It Works