-
Notifications
You must be signed in to change notification settings - Fork 238
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
Expand GenAI project to cover instrumentation libraries #2326
Conversation
Thank you for bringing this topic up @lmolkova . From Langtrace, myself and my colleague, Ali are happy to contribute/maintain/approve the channges. |
Tagging more people in the community who might be interested to work on instrumentation libraries @AmanAgarwal041 @cartermp @codefromthecrypt @langchain4j @trentm |
@lmolkova happy to assist here! I think my co-founder @galkleinman would also want to participate |
@lmolkova More than happy to help here! |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Very happy to see this taking shape!
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
A couple org/scope related questions which are possibly just because I am new to how things are structured. Please forgive if they are misplaced.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Great to see this in motion, Few nits as to keep vendor neutrality from this proposal. Me and @AmanAgarwal041 are happy to contribute instrumentations from https://github.com/openlit/openlit aswell
1d8067b
to
7bd84b4
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I used to maintain js and python for zipkin and currently dusting off my skills, reviewing and maintaining these languages again.
If you need another approver who will pull changes local, test them, verify against current practice, etc before clicking ✔️ , feel free to use me. There's a lot of work to do, and I suspect this will help keep wheels in APAC moving.
I'd be happy to sponsor this SIG |
Co-authored-by: Riccardo Magliocchetti <[email protected]>
Co-authored-by: Riccardo Magliocchetti <[email protected]>
Co-authored-by: patcher9 <[email protected]> Co-authored-by: Emily S <[email protected]>
Co-authored-by: Adrian Cole <[email protected]>
b96af37
to
0b22f8b
Compare
Based on the discussions in LLM semconv group, we'd like to suggest expanding the scope of the group to cover instrumentation libraries.
The long-term goal of the project is:
We intend to add instrumentations one-by-one and limit features to those documented in semantic conventions. Instrumentations will evolve along with semconv, but may provide additional hooks or opt-in features allowing to customize them to specific vendor needs.
We're going to request
opentelemetry-genai
repo for the coordination/project management, but may request additional repos later to host WIP gen-ai instrumentation libraries when using existing contrib repos is problematic. with the long-term goal to contribute them upstream or merge to contrib once possible.We're looking for engineers to work on instrumentation libraries, especially in JavaScript and existing JS-contrib approvers/maintainers to help with code review, best practices and general OTel.
/cc @alolita @tedsuo @trask @nirga @drewby @karthikscale3 @lzchen