Skip to content

Propose an update to the values of 'gen_ai.system' for Google.#2050

Merged
trask merged 10 commits intoopen-telemetry:mainfrom
michaelsafyan:google_genai_system
Apr 16, 2025
Merged

Propose an update to the values of 'gen_ai.system' for Google.#2050
trask merged 10 commits intoopen-telemetry:mainfrom
michaelsafyan:google_genai_system

Conversation

@michaelsafyan
Copy link
Copy Markdown
Contributor

Fixes #1950

Changes

Refines the values of gen_ai.system for Google's AI products.

The Google Gen AI SDK defined here:

... provides a common client for both the Vertex AI and Gemini APIs and reflects some degree of intended sharing / convergence between these two systems. Having totally separate names (like vertex_ai and gemini) without a common prefix means that any vendor-specific attributes would need to be defined duplicatively for both vertex_ai and for gemini, even if supported by both systems.

Additionally, code built on top of the Google Gen AI SDK may not necessarily know which backend is being used.

This change proposes a common prefix (gcp.gen_ai) which may be used for any Google-specific Gen AI attributes that are common between both backend systems. More specific sub-systems (gcp.gen_ai.vertex_ai and gcp.gen_ai.gemini) still exist to allow for divergent properties where desireable. However, the common prefix should make it easier to provide unified Semantic Conventions where it makes sense to do so, simplifying conventions and instrumentation.

Merge requirement checklist

  • CONTRIBUTING.md guidelines followed.
  • Change log entry added, according to the guidelines in When to add a changelog entry.
    • If your PR does not need a change log, start the PR title with [chore]
  • [?] schema-next.yaml updated with changes to existing conventions.
    • Is it possible to rename attribute values this way? I see that attribute keys are renamable, but it's not clear whether it is possible to change the values this way.

Comment thread docs/attributes-registry/gen-ai.md Outdated
Comment thread docs/attributes-registry/gen-ai.md Outdated
Comment thread docs/attributes-registry/gen-ai.md Outdated
Comment thread .chloggen/gcp_genai_system.yaml Outdated
Comment thread docs/attributes-registry/gen-ai.md Outdated
Comment thread model/gen-ai/registry.yaml Outdated
@michaelsafyan michaelsafyan requested a review from lmolkova April 10, 2025 17:55
Comment thread model/gen-ai/registry.yaml Outdated
@lmolkova lmolkova moved this from Untriaged to Needs More Approval in Semantic Conventions Triage Apr 13, 2025
@lmolkova lmolkova added this pull request to the merge queue Apr 16, 2025
@github-merge-queue github-merge-queue Bot removed this pull request from the merge queue due to failed status checks Apr 16, 2025
@jsuereth jsuereth added this pull request to the merge queue Apr 16, 2025
@github-merge-queue github-merge-queue Bot removed this pull request from the merge queue due to failed status checks Apr 16, 2025
@trask trask merged commit 47fe2c0 into open-telemetry:main Apr 16, 2025
14 of 15 checks passed
lmolkova pushed a commit to lmolkova/semantic-conventions that referenced this pull request May 13, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Projects

Archived in project

Development

Successfully merging this pull request may close these issues.

Rename gen_ai.system values of vertex_ai and gemini

5 participants