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

🚀 Feature: Instrument the new google genai library #2675

Open
1 task done
dinmukhamedm opened this issue Feb 23, 2025 · 3 comments
Open
1 task done

🚀 Feature: Instrument the new google genai library #2675

dinmukhamedm opened this issue Feb 23, 2025 · 3 comments

Comments

@dinmukhamedm
Copy link
Contributor

Which component is this feature for?

Google Generative AI Instrumentation

🔖 Feature description

We need a separate package, perhaps opentelemetry-instrumentation-genai to instrument google's newer google-genai SDK.

  1. https://pypi.org/project/google-genai/
  2. https://discuss.ai.google.dev/t/google-generativeai-vs-python-genai/53873/

🎤 Why is this feature needed ?

As per discussion link [2] above, the library will eventually replace the older lower-level APIs.

✌️ How do you aim to achieve this?

By creating a separate instrumentation library

🔄️ Additional Information

No response

👀 Have you spent some time to check if this feature request has been raised before?

  • I checked and didn't find similar issue

Are you willing to submit PR?

None

@dinmukhamedm
Copy link
Contributor Author

@nirga actually I am willing to submit a PR, but have no time to do this now. So I am happy if somebody else in the community picks this up.

Also, how does this align with #2456? Should the new library already send just events or should we start with attributes for now?

@nirga
Copy link
Member

nirga commented Feb 23, 2025

@dinmukhamedm for #2456 the goal is to start sending both events and attributes to align with approved otel semantic conventions while easing migration. In the long term, we might have a mechanism in the SDK to translate events -> attributes. That way, the instrumentations themselves can be aligned with semantic conventions (emitting events) while the SDK keeps the way we work today (which is better IMO 😅 ).

@TheMellyBee
Copy link

I am also in need of this!

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

No branches or pull requests

3 participants