open-telemetry / open-telemetry/opentelemetry-java-instrumentation

Migrate the semantic conventions of OpenAI instrumentation to 1.37.0.

Open
#15,174 7 comments 1 reaction 0 assignees View on GitHub

Nobody has claimed this yet.

enhancement needs triage
Dominant language
Java
Stars
2.6k
Forks
1.2k
Avg merge
2d 18h
Merged PRs (30d)
228

Description

Is your feature request related to a problem? Please describe.

The implementation of the OpenAI instrumentation is based on semconv version 1.36.0, which includes significant updates in version 1.37.0, such as redefining the schema of message events, introducing configuration options to control data-capturing behaviors, and adding more important attributes.

Describe the solution you'd like

I believe we need to refactor the OpenAI instrumentation to align with the latest semantic conventions for capturing chat messages. I have previously submitted a draft PR for this. If possible, I hope to resolve this issue, as it will also benefit the development of #14783 and #12878.

cc @anuraaga

Describe alternatives you've considered

No response

Additional context

No response

Tip

React with 👍 to help prioritize this issue. Please use comments to provide useful context, avoiding +1 or me too, to help us triage it. Learn more here.

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by reviewing draft PR #14613 and the OpenAI instrumentation changes it proposes, then compare the current implementation with semantic conventions 1.37.0. Done means the instrumentation follows the updated message-event schema, supports the described data-capture configuration options, and includes the additional attributes while addressing the related issues #14783 and #12878.

Written by the indexing model from the issue text.

Assessment

Tech stack
java
Domain
observability-sre
Issue type
Refactor
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.