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
Hello 👋 The latest OTel Gen AI semantic conventions put prompt content into OTel Log Events instead of Span attributes/events. In particular, it would be great to see this for LangChain/LangGraph instrumentations.
🎤 Why is this feature needed ?
So telemetry matches the current OTel semantic conventions
✌️ How do you aim to achieve this?
I haven't been joining the GenAI Semconv WG meetings and don't know the current plan. If the plan is to move instrumentation into OTel, I can work on that and implement it in OTel repos.
Otherwise, I can send PRs here.
🔄️ Additional Information
No response
👀 Have you spent some time to check if this feature request has been raised before?
There is #1455 but it doesn't mention log events specifically
I checked and didn't find similar issue
Are you willing to submit PR?
Yes I am willing to submit a PR!
The text was updated successfully, but these errors were encountered:
Which component is this feature for?
Langchain Instrumentation
🔖 Feature description
Hello 👋 The latest OTel Gen AI semantic conventions put prompt content into OTel Log Events instead of Span attributes/events. In particular, it would be great to see this for LangChain/LangGraph instrumentations.
🎤 Why is this feature needed ?
So telemetry matches the current OTel semantic conventions
✌️ How do you aim to achieve this?
I haven't been joining the GenAI Semconv WG meetings and don't know the current plan. If the plan is to move instrumentation into OTel, I can work on that and implement it in OTel repos.
Otherwise, I can send PRs here.
🔄️ Additional Information
No response
👀 Have you spent some time to check if this feature request has been raised before?
There is #1455 but it doesn't mention log events specifically
Are you willing to submit PR?
Yes I am willing to submit a PR!
The text was updated successfully, but these errors were encountered: