feat(browser): Expose vercelai instrumentation#18347
feat(browser): Expose vercelai instrumentation#18347nicohrubec wants to merge 3 commits intodevelopfrom
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.
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.