[bot] OpenAI inline moderation (`moderation` param/field) not captured on Chat Completions or Responses API spans
Personne n'a encore pris cette issue.
Évaluation
- Difficulté
- 3/5
- Temps estimé
- 1-2 jours
- Accessibilité débutants
- 64/100
- Type d'issue
- Fonctionnalité
- Clarté
- Clairement spécifiée
- Activité
- Active
- Stack technique
- ruby
- Domaine
- ai-infra-agents, observability
Piste de recherche
Start by reading the four named instrumentation files: the Chat and Responses implementations for both openai and ruby-openai. Trace how each METADATA_FIELDS list and finalize_metadata method collects request and response data, then inspect the related tests to see how metadata is asserted. Done means inline moderation configuration and results are captured on both API spans across both integrations.
Rédigé par le modèle d'indexation à partir du texte de l'issue.
Description
<!-- provider-gap-audit: openai-inline-moderation-not-captured -->
Summary
OpenAI's Chat Completions and Responses APIs support an official moderation request parameter that runs moderation on the request input and generated output in the same call, returning the results in a moderation field on the response. This is distinct from the standalone moderations.create endpoint (which this SDK already instruments). Neither the request parameter nor the response field is captured anywhere in this repo's openai or ruby-openai instrumentation, for either Chat Completions or the Responses API.
What is missing
Request parameter
moderation: { model:, policy: { input: { mode: }, output: { mode: } } }— configures which moderation model to run and whether to just score or actively block input/output.
Response field
ChatCompletion#moderation—{ input: ModerationResult|Error, output: ModerationResult|Error }Response#moderation— same shape, on the Responses API'sResponseobject
Neither field appears in any METADATA_FIELDS list, and neither finalize_metadata method reads the response's moderation attribute, so a moderated call's safety signals are silently dropped from the trace in all four affected instrumentation files.
Braintrust docs status
not_found — https://docs.braintrust.dev/integrations/ai-providers/openai documents a dedicated "Moderation" span type tied to moderations.create (and openai.moderations.create for Ruby) as a standalone endpoint, but has no mention of inline moderation results being captured as part of chat completion or Responses spans, for any language SDK.
Upstream sources
- Official OpenAI Ruby SDK:
OpenAI::Chat::CompletionCreateParamsdefinesoptional :moderation, -> { OpenAI::Chat::CompletionCreateParams::Moderation }("Configuration for running moderation on the request input and generated output.") — https://github.com/openai/openai-ruby/blob/main/lib/openai/models/chat/completion_create_params.rb OpenAI::Chat::ChatCompletiondefinesoptional :moderation, -> { OpenAI::Chat::ChatCompletion::Moderation }("Moderation results for the request input and generated output, if moderated completions were requested.") — https://github.com/openai/openai-ruby/blob/main/lib/openai/models/chat/chat_completion.rbOpenAI::Responses::ResponseCreateParamsandOpenAI::Responses::Responsedefine the equivalentmoderationrequest/response fields — https://github.com/openai/openai-ruby/blob/main/lib/openai/models/responses/response_create_params.rb and.../responses/response.rb- OpenAI changelog / announcement: moderation scores added to the Responses API and Chat Completions API (June 2026) — https://developers.openai.com/api/docs/changelog and https://platform.openai.com/docs/api-reference/chat/create
Local repo files inspected
lib/braintrust/contrib/openai/instrumentation/chat.rb(METADATA_FIELDSat lines 27–32;finalize_metadataat lines 129–136) — nomoderationlib/braintrust/contrib/openai/instrumentation/responses.rb(METADATA_FIELDSat lines 26–31;finalize_metadataat lines 109–112) — nomoderationlib/braintrust/contrib/ruby_openai/instrumentation/chat.rb(METADATA_FIELDSat lines 32–37;finalize_metadataat lines 137–143) — nomoderationlib/braintrust/contrib/ruby_openai/instrumentation/responses.rb(METADATA_FIELDSat lines 32–37;finalize_metadataat lines 137–140) — nomoderationlib/braintrust/contrib/openai/instrumentation/moderations.rb— confirms this SDK already treats moderation as a first-class signal worth tracing, just not when it arrives inline on a generation call
- Langage dominant
- Ruby
- Étoiles
- 9
- Forks
- 11
- Merge moyen
- 1 j 11 h
- PR mergées (30 j)
- 3
Préparer son environnement
- Fournit un Dockerfile ou un fichier Docker Compose
- Aucun modèle de pull request
- Lire le guide de contribution
Par où commencer
- Lisez l'issue en entier, puis le guide de contribution du projet.
- Signalez en commentaire que vous la prenez — cela évite que deux personnes fassent le même travail.
- Forkez le dépôt et travaillez sur une branche.
- Ouvrez une pull request qui référence le numéro de l'issue.
Autres issues de braintrustdata/braintrust-sdk-ruby
-
Difficulté 2/5 1-3 heures Accessibilité débutants 82/100
-
[bot] OpenAI Responses API `compact()` (server-side conversation compaction) not instrumentedOuverte
Difficulté 2/5 1-3 heures Accessibilité débutants 78/100
-
Difficulté 2/5 1-3 heures Accessibilité débutants 78/100
-
[BOT ISSUE] OpenAI Chat Completions missing reasoning model and web search metadata parametersOuverte
Difficulté 2/5 1-3 heures Accessibilité débutants 76/100
-
Difficulté 2/5 1-3 heures Accessibilité débutants 72/100
Toutes les issues de braintrustdata/braintrust-sdk-ruby
Issues similaires
-
Difficulté 2/5 1-3 heures Accessibilité débutants 74/100
Les mainteneurs répondent en général sous 1 jour
-
Websockify heartbeat for vnc_containerPeut-être pris @robinkar l’a pris aujourd’hui. Ouverte
Difficulté 2/5 1-3 heures Accessibilité débutants 76/100
Les mainteneurs répondent en général sous 1 jour
-
needs verification
Difficulté 2/5 1-3 heures Accessibilité débutants 68/100
Les mainteneurs répondent en général sous 7 jours
-
Difficulté 1/5 Moins d'une heure Accessibilité débutants 88/100
akitaonrails/ai-book-2026#13 ·
-
Mend: dependency security vulnerability
Difficulté 2/5 1-3 heures Accessibilité débutants 63/100
Les mainteneurs répondent en général sous 1 jour