feat: improve LangWatch integration by introducing langchain callbacks on the tracing service, and component and workflow span types #3094
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
dosubot
bot
added
size:L
|
This pull request is automatically being deployed by Amplify Hosting (learn more). |
…he tracing service, and component and workflow span types. Bump LangWatch to v0.1.14
ogabrielluiz
changed the title
github-actions
bot
added
enhancement
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Bump LangWatch to v0.1.14
For this flow:
Before:
After:
Now it's much better on mapping directly to workflow and components 1 to 1, and the langchain steps inside it so capturing the LLM call precisely to get the cost, tokens etc. Tested with agents, tools, multiple llm calls and so on, the tracing is quite robust now
agent.mp4
(tool capturing was indeed correct on the video as well)