You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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.
The text was updated successfully, but these errors were encountered:
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.
The text was updated successfully, but these errors were encountered: