-
-
Notifications
You must be signed in to change notification settings - Fork 1.7k
feat(browser): Expose vercelai instrumentation #18347
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
Conversation
size-limit report 📦
|
| // These tests are not exhaustive because the instrumentation is | ||
| // already tested in the node integration tests and we merely | ||
| // want to test that the instrumentation does not crash in the browser | ||
| // and that gen_ai transactions are sent. | ||
|
|
||
| sentryTest('manual Vercel AI instrumentation sends gen_ai transactions', async ({ getLocalTestUrl, page }) => { |
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.
m: I don't have a super strong opinion here but given node and browser do have their differences, I'd prefer a bit stricter tests where we test against more data. Helps us find issues as well. Ill also defer to @RulaKhaled for the final call. Whatever you think makes most sense :)
Update: I bumped this to logaf-M: Can we check against some data that should be aded from our instrumentation? The attribute we check against is from the manually started span, no?
|
Sorry, I dismissed my review because @andreiborza brought up an important question around this being effective in browser. Let's clarify this first. Happy to re-✅ afterwards |
|
Closing this as we don't use Otel in the browser so using the Vercel span processor in the browser doesn't do anything. |
We are exposing AI instrument methods for VercelAI enabling users to use it directly from the browser SDK.