Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Define a more structured alternative to gen_ai.operation.name #1948

Open
michaelsafyan opened this issue Feb 27, 2025 · 0 comments
Open

Define a more structured alternative to gen_ai.operation.name #1948

michaelsafyan opened this issue Feb 27, 2025 · 0 comments

Comments

@michaelsafyan
Copy link
Contributor

michaelsafyan commented Feb 27, 2025

Area(s)

area:gen-ai

What's missing?

The ability to define gen_ai.operation.name more flexibly.

To allow for more flexible naming of gen_ai.operation.name, I think there should exist a different attribute that aims to define the type/kind/category of GenAI operation in a closed set of allowable values.

Describe the solution you'd like

It would be ideal to create a new attribute like:

  • gen_ai.operation.type

... to provide a more structured representation, allowing for name to be made flexible.

I'm not sure what values should be provided, but a strawman might be something like:

  • tokens.embeddings.create
  • contexts.cache.create
  • contexts.cache.update
  • models.content.generate
  • chats.sessions.create
  • agents.agent.create
  • agents.agent.execute
  • agents.group.create
  • agents.group.execute

I'm open to other ideas regarding the values, but I think it would be a good idea to have some hierarchy/grouping in the value to make this sustainable in the long run.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Development

No branches or pull requests

1 participant