-
Notifications
You must be signed in to change notification settings - Fork 42
feat: instrumentation for chromadb #79
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
Merged
Merged
Changes from 82 commits
Commits
Show all changes
94 commits
Select commit
Hold shift + click to select a range
991c7c1
init: instrumentation setup for chromadb
5war00p 6e9a236
fix: sample app
5war00p f6a1420
config: chromadb package version
5war00p a6051e1
Merge branch 'main' into instrumentation-chroma
5war00p c99b3fb
sample with all required functions
5war00p eda1f81
instrumentation with basic wrapperMethod
5war00p d0e1d0e
feat: event tracking only for query and peek
5war00p b49a700
fix(sdk): protect against failures to JSON.stringify() input/output (…
nirga 7725596
v0.5.1
nirga adc929b
fix(sdk): log input/output Maps (#94)
nirga da64151
v0.5.2
nirga d6bfca5
chore(deps): bump @aws-sdk/client-bedrock-runtime from 3.504.0 to 3.5…
dependabot[bot] 85cdc5b
fix(sdk): input/output logging with content tracing override (#100)
nirga 7f7aef9
v0.5.3
nirga 30d4bce
fix(llamaindex): support v0.1.0 (#102)
nirga 80966b3
v0.5.4
nirga bbdb8f9
fix(llamaindex): chat engine
nirga a6134e5
v0.5.5
nirga 9b8be9e
v0.5.6
nirga fbf7b8e
fix(sdk): webpack import issues
nirga 8904b30
v0.5.7
nirga eaaa086
fix(sdk): nextjs build errors (#126)
nirga a2e8200
v0.5.8
nirga 42e30ec
chore: temporarily disabled cohere tests (#127)
nirga 34efd31
fix: build SDK with rollup (#125)
nirga 56b43fa
v0.5.9
nirga 2fdccf5
fix(sdk): module files
nirga 2a432d3
v0.5.10
nirga 4314ff7
fix(sdk): revert back to tsc
nirga aa9cfe4
v0.5.11
nirga 303d002
fix(sdk): nextjs bug; tests
nirga d6345c5
v0.5.12
nirga c21c02f
fix(langchain): manually instrument (#128)
nirga 93c03e3
v0.5.13
nirga 957eb70
fix(langchain): report input/output (#131)
nirga 5db1cf5
fix(llamaindex): report inputs/outputs (#132)
nirga bd67faa
v0.5.14
nirga 6899607
fix(sdk): require instead if import
nirga 5ccf242
v0.5.15
nirga e4fa1eb
fix(langchain): can't add openLLMetryPatched
nirga 5bc0c91
v0.5.16
nirga d64078c
fix(sdk): switched back to rollup
nirga 8fe74f2
v0.5.17
nirga 72198b3
fix: proper tracer fetcing in llamaindex and langchain
nirga d59e6e2
v0.5.18
nirga 35631df
v0.5.19
nirga 14e2adc
fix(sdk): use cross-fetch to avoid require() use errors (#143)
nirga dae0003
v0.5.20
nirga 8d66d2d
fix: do not patch modules (#146)
nirga 0427aa5
v0.5.21
nirga e96758c
init: instrumentation setup for chromadb
5war00p b5532cc
fix: typo fix for peek
5war00p c7ca26c
fix: llamaindex query issue on sample app
5war00p b2c1d3e
fix: node-server instrumentation
5war00p 629fad9
fix: package-lock
5war00p 4c26378
Merge branch 'main' into instrumentation-chroma
5war00p c2f836f
fix: package-lock
5war00p 3a40b2e
fix: lint errors
5war00p 4f311a3
fix: prettier issues
5war00p ccf00d7
fix: requested changes from review
5war00p 4221aad
Merge branch 'main' into instrumentation-chroma
5war00p 964bdc6
feat: added real example for chroma sample
5war00p 77e7847
Merge branch 'main' into instrumentation-chroma
5war00p 7e68f5b
fix: chroma added to node-server
5war00p 90e3f33
fix: pinecone config
5war00p 8d956fb
Revert "fix: pinecone config"
5war00p 9db5a1e
fix: chromadb instrumentation add fix
5war00p 8028a8a
fix: build errors
5war00p 2183724
fix: readme
5war00p c5c08c1
fix: set vector spans only on trace content true
5war00p 619350a
Merge branch 'main' into instrumentation-chroma
5war00p f8bd945
feat: event based attributes tracking
5war00p 1fa95db
fix: split sample apps into multiple files
5war00p 3e07d59
fix: prettier issues
5war00p f378220
fix: individual events for each result
5war00p fad0112
fix: remove n+1 array iteration for response attributes
5war00p 3d3721c
feat: test cases for chromadb
5war00p 516bea4
fix: setAllAttributes at once
5war00p 332a519
feat: added chromadb sping up programmatically in tests
5war00p 6cb2906
fix: add timeout after shell instantiation
5war00p effbee1
fix: increase timeout to 5sec
5war00p 2e2c0ba
fix: timeout and remove commented code
5war00p 5b9c957
fix: unskip skipped tests
5war00p 6f9d1cf
ci: add python package in workflow
5war00p fc68b14
fix: push exiting code
5war00p 2f9ce7b
docs: comment for process kill
5war00p 8607052
fix: span event attributes
5war00p 0a768db
fix: asserts for event attributes
5war00p 815e1ad
fix: change gitignore chroma sqllite3
5war00p 40d4ed6
Update packages/instrumentation-chromadb/src/instrumentation.ts
nirga 31779a5
Merge branch 'main' into instrumentation-chroma
nirga 8a5f8b2
fix(chromadb): exception logger
nirga 4550e4d
Merge branch 'main' into pr/79
nirga 5c8cb3b
chore: readme
nirga File filter
Filter by extension
10000
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
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
Oops, something went wrong.
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.
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.
why?
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.
So when we run chromadb locally it creates the files do we need to commit those? It should be local right?