Area(s)

area:gen-ai

What's missing?

Instrumentation library for google-genai here:

https://github.com/open-telemetry/opentelemetry-python-contrib/tree/6bde73ce344af1df7002bc001ad0fc7d51b4b577/instrumentation-genai/opentelemetry-instrumentation-google-genai

... adds generate_content as a value for gen_ai.operation.name:

https://github.com/open-telemetry/opentelemetry-python-contrib/blob/6bde73ce344af1df7002bc001ad0fc7d51b4b577/instrumentation-genai/opentelemetry-instrumentation-google-genai/src/opentelemetry/instrumentation/google_genai/generate_content.py#L52

https://github.com/open-telemetry/opentelemetry-python-contrib/blob/6bde73ce344af1df7002bc001ad0fc7d51b4b577/instrumentation-genai/opentelemetry-instrumentation-google-genai/src/opentelemetry/instrumentation/google_genai/generate_content.py#L229

This should be captured in Semantic Conventions.

Describe the solution you'd like

For now, simply define generate_content as an additional permissible value.

Separately, there are issues covering revisiting the meaning/scope in general of this operation name:

• Refine gen_ai.operation.name to be defined in a way that allows for looser naming semantic-conventions-genai#21
• Define a more structured alternative to gen_ai.operation.name semantic-conventions-genai#20

... but those larger scope changes should be independent of the small incremental act of updating the Semantic Conventions to reflect the reality of instrumentation.

I've already drafted a small change to add generate_content as a documented value:

• https://github.com/michaelsafyan/open-telemetry.semantic-conventions/tree/generate_content

I'm creating this issue as a point of reference for the CHANGELOG to go with the draft change. I intend to send a pull request soon.