open-telemetry / open-telemetry/opentelemetry-python

Add Support for `gen_ai` semantic-convention breaking changes in v1.37.0

Open
#4,878 3 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

feature-request
Dominant language
Python
Stars
2.6k
Forks
1k
Avg merge
4d 15h
Merged PRs (30d)
19

Description

Is your feature request related to a problem?

The gen_ai fields are not using the latest semantic convention. It looks like this was supposed to be done in this PR https://github.com/open-telemetry/opentelemetry-python/pull/4731/changes#diff-25ace29f4af9b016a152aad40987138b245a5dcee698581ecdcb3fb106455b58 but using the latest sdk version v1.39.1, it appears the gen_ai fields are still using the only semantic convention (labels.gen_ai_prompt).

Describe the solution you'd like

In the v1.37.0 release https://github.com/open-telemetry/semantic-conventions/releases/tag/v1.37.0, it added breaking changers for gen_ai fields. Can we double check that the fields are properly ingested and follow the latest convention.

Describe alternatives you've considered

No response

Additional Context

No response

Would you like to implement a fix?

None

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 comparing the current gen_ai fields, including labels.gen_ai_prompt, with the OpenTelemetry semantic-conventions v1.37.0 release. Review PR 4731 and verify the behavior against SDK version v1.39.1. Done means the fields are properly ingested and follow the latest gen_ai convention.

Written by the indexing model from the issue text.

Assessment

Tech stack
python
Domain
observability
Issue type
Feature
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.