Upgrade ts telemetry instrumentation #2030
Merged
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
csansoon
force-pushed
the
upgrade-ts-telemetry-instrumentation
branch
from
4fb5a03 to
027b9a8
Compare
csansoon
force-pushed
the
upgrade-ts-telemetry-instrumentation
branch
from
027b9a8 to
211fc8d
Compare
csansoon
force-pushed
the
upgrade-ts-telemetry-instrumentation
branch
from
211fc8d to
d2c2f60
Compare
| "@traceloop/instrumentation-llamaindex": "0.22.2", | ||
| "@traceloop/instrumentation-openai": "0.22.2", | ||
| "@traceloop/instrumentation-together": "0.22.2", | ||
| "@traceloop/instrumentation-vertexai": "0.22.2", |
Contributor
There was a problem hiding this comment.
Should be optional dependencies. And when you want to install Vertex for example you install this package? Otherwise, are we loading all these packages for everyone?
Contributor
Author
There was a problem hiding this comment.
We are loading these packages for everyone. The idea is that integrating latitude telemetry in your app should be as simple and fast as possible
Contributor
There was a problem hiding this comment.
But it adds more bloat to everyone. Just saying
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
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.
Fixed traceloop instrumentation
Traceloop instrumentation packages were all either outdated or deprecated. All of the packages have been upgraded or removed to use the latests supported versions.
Removed package-specific types
The
LatitudeTelemetryclass constructor is expected to be used with aninstrumentationsattribute, containing the class or package from your provider's official SDK. (Almost) every value was typed with the expected class or object, but this lead to type errors when the package version was off by even a patch. They've all been changed to "any" to mitigate this issue and reduce package size. Now, you must head to the documentation to know exactly what is expected.Integrations Documentation
Speaking of docs, there's a new (hidden) tab in the documentation, displaying how to connect Latitude Telemetry to an existing JS project, with all our current supported providers and frameworks. This documentation is hidden for now, because some of these providers still don't work as expected, which will be solved in the next PR.