feat(sync): create spans to accurately record token usage#1
Open
GoldenChrysus wants to merge 1 commit into
Open
feat(sync): create spans to accurately record token usage#1GoldenChrysus wants to merge 1 commit into
GoldenChrysus wants to merge 1 commit into
Conversation
This file contains hidden or 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
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.
Found this tool today and excited to use it, but found that it doesn't do the one thing I wanted to use it for: observing my Bedrock costs in Opik.
Current implementation only creates traces instead of spans, so I've added functionality to create a span per assistant message.
I also fixed an issue where the tool currently doesn't respect the Opik project name at all.
Claude Codeis hard-coded as the value no matter what is present in the config file or env variables.Sorry for all the white space changes. LSP does not like all the extra white space...