Hacktoberfest 2026: die Issues, die Maintainer für den Oktober markiert haben – offen und einsteigerfreundlich. Hacktoberfest-Issues durchsuchen

[bot] OpenAI: Realtime API (`client.realtime.connect()`) has zero instrumentation

Offen
#798 0 Kommentare 0 Reaktionen 0 zugewiesene Personen Auf GitHub ansehen

Dieses Issue hat noch niemand übernommen.

Bewertung

Schwierigkeit
4/5
Geschätzter Aufwand
3-5 Tage
Anfängerfreundlichkeit
45/100
Issue-Typ
Feature
Klarheit
Klar beschrieben
Aktivitätsstatus
Aktiv
Tech-Stack
python

Rechercherichtung

The missing instrumentation is for the OpenAI Python SDK's Realtime API (client.realtime.connect()). Start by examining the existing patchers in py/src/braintrust/integrations/openai/patchers.py and the integration setup in integration.py. Review the upstream OpenAI SDK's realtime module to understand the connection manager and event flow. The goal is to add a new patcher for the realtime resource, creating spans for the WebSocket session and individual events, similar to the existing Responses API instrumentation. Testing will involve verifying the new spans appear when using the realtime API.

Vom Indexierungsmodell aus dem Issue-Text verfasst.

Beschreibung

Summary

The OpenAI Python SDK's top-level Realtime/AsyncRealtime resource (client.realtime.connect() / client.realtime.client_secrets / client.realtime.calls) — the GA WebSocket API for real-time audio/text/tool-use sessions — has no instrumentation anywhere in this repo. This is a distinct, self-contained SDK surface from client.responses.connect() (already tracked in #188): it lives in its own module with its own connection manager and does not share implementation with the Responses API's websocket transport.

What is missing

py/src/braintrust/integrations/openai/integration.py registers exactly these patchers:

patchers = (
    AgentsSessionsPatcher,
    ChatCompletionsPatcher,
    EmbeddingsPatcher,
    ModerationsPatcher,
    AudioSpeechPatcher,
    AudioTranscriptionsPatcher,
    AudioTranslationsPatcher,
    ImagesPatcher,
    ResponsesPatcher,
)

py/src/braintrust/integrations/openai/patchers.py's _WRAP_TARGETS registry (the authoritative list of every OpenAI SDK method this repo patches) contains no realtime entry:

_WRAP_TARGETS: tuple[tuple[str, type[CompositeFunctionWrapperPatcher]], ...] = (
    ("beta.agents.sessions", _WrapAgentsSessions),
    ("chat.completions", _WrapChatCompletions),
    ("embeddings", _WrapEmbeddings),
    ("moderations", _WrapModerations),
    ("audio.speech", _WrapAudioSpeech),
    ("audio.transcriptions", _WrapAudioTranscriptions),
    ("audio.translations", _WrapAudioTranslations),
    ("images", _WrapImages),
    ("responses", _WrapResponses),
    ("responses.with_raw_response", _WrapResponsesRaw),
    ("beta.chat.completions", _WrapChatCompletions),
)

A case-insensitive search for "realtime" across the entire py/src/braintrust tree returns zero hits related to OpenAI's Realtime API (the only matches are unrelated "real-time" prose in other integrations/docs). At minimum, instrumentation should provide a session-level span for connect() (model config, duration, aggregate usage) and turn/tool-call spans for events sent/received over the WebSocket connection, mirroring the pattern already used for streaming responses.

Braintrust docs status: not_found

The OpenAI integration page documents Chat Completions, Responses, Embeddings, Moderation, Batch, and the Agents API as traced. It does not describe any tracing support for the Realtime API or client.realtime/connect() — the only "realtime" mention on the page is a cookbook link title ("Evaluating audio with the OpenAI Realtime API"), with no SDK-level tracing detail.

Upstream sources

Local repo files inspected

  • py/src/braintrust/integrations/openai/integration.py (full file)
  • py/src/braintrust/integrations/openai/patchers.py (_WRAP_TARGETS registry)
  • Repo-wide case-insensitive grep for realtime across py/src/braintrust
Vorherrschende Sprache
Python
Sterne
19
Forks
17
Ø Merge
1 T. 5 Std.
Gemergte PRs (30 T.)
61

Beitragsleitfaden

Beitragsleitfaden öffnen

Erste Schritte

  1. Lesen Sie das ganze Issue und danach den Beitragsleitfaden des Projekts.
  2. Schreiben Sie ins Issue, dass Sie es übernehmen — das erspart doppelte Arbeit.
  3. Forken Sie das Repository und arbeiten Sie in einem Branch.
  4. Öffnen Sie einen Pull Request, der die Issue-Nummer nennt.

Mehr aus braintrustdata/braintrust-sdk-python

Alle Issues in braintrustdata/braintrust-sdk-python

Ähnliche Issues

Weitere Issues zu Python

Neue Issues direkt in Ihr Postfach

Eine kurze Übersicht über anfängerfreundliche GitHub-Issues.