Add openai.api.type attribute to distinguish OpenAI API types#3337
Merged
lmolkova merged 5 commits intoopen-telemetry:mainfrom Feb 17, 2026
Merged
Conversation
lmolkova
reviewed
Jan 26, 2026
joaopgrassi
moved this from Untriaged
to Awaiting codeowners approval
in Semantic Conventions Triage
lmolkova
reviewed
Feb 4, 2026
singankit
changed the title
responses operation value to gen_ai.operation.name
singankit
force-pushed
the
users/singankit/responses_operation
branch
from
e1ea320 to
04966b6
Compare
lmolkova
reviewed
Feb 10, 2026
singankit
force-pushed
the
users/singankit/responses_operation
branch
from
04966b6 to
9f63c01
Compare
Add support for OpenAI Responses API operation type in the gen_ai.operation.name attribute.
…t enum - Rename gen_ai.api.type to openai.api.type (OpenAI-specific attribute) - Remove 'version' from brief description - Change from free-form string to strict enum (chat_completions, responses) - Remove stale 'responses' operation value from gen_ai.operation.name docs - Update OpenAI registry docs with new attribute
singankit
force-pushed
the
users/singankit/responses_operation
branch
from
72bdfed to
02d73dd
Compare
lmolkova
approved these changes
Feb 10, 2026
lmolkova
moved this from Awaiting codeowners approval
to Needs More Approval
in Semantic Conventions Triage
wrisa
approved these changes
Feb 17, 2026
aabmass
approved these changes
Feb 17, 2026
Copilot AI
added a commit
to dotnet/extensions
that referenced
this pull request
Feb 17, 2026
Implements the OpenTelemetry semantic convention for distinguishing OpenAI API types (open-telemetry/semantic-conventions#3337). - OpenAIChatClient adds openai.api.type=chat_completions - OpenAIResponsesChatClient adds openai.api.type=responses - Both check Activity.Current for a matching "chat" span from OpenTelemetryChatClient - Added tests for both streaming and non-streaming scenarios Co-authored-by: stephentoub <[email protected]>
nagkumar91
pushed a commit
to nagkumar91/semantic-conventions
that referenced
this pull request
Feb 24, 2026
6 tasks
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
6 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Add openai.api.type attribute to distinguish OpenAI API types
Fixes #
Changes
Please provide a brief description of the changes here.
Important
Pull requests acceptance are subject to the triage process as described in Issue and PR Triage Management.
PRs that do not follow the guidance above, may be automatically rejected and closed.
Merge requirement checklist
[chore]