feat(node): Add eveInstrumentation and eveIntegration for eve apps - #24539
Merged
Merged
Conversation
Contributor
size-limit report 📦
|
![cursor[bot]](https://avatars.githubusercontent.com/in/1210556?s=60&v=4){kind=small}
There was a problem hiding this comment.
Cursor Bugbot has reviewed your changes and found 1 potential issue.
❌ Bugbot Autofix is OFF. To automatically fix reported issues with cloud agents, enable autofix in the Cursor dashboard.
Reviewed by Cursor Bugbot for commit db2143c. Configure here.
JPeer264
reviewed
Sep 21, 2026
JPeer264
left a comment
JPeer264
left a comment
Member
There was a problem hiding this comment.
It's a draft so I won't approve (not sure if it will change still), but overall it looks good
| "@sentry/node": "file:../../packed/sentry-node-packed.tgz", | ||
| "ai": "^7.0.82", | ||
| "dataloader": "^2.2.3", | ||
| "eve": "^0.52.3", |
Member
There was a problem hiding this comment.
q: Do we still support the older versions?
Member
Author
There was a problem hiding this comment.
technically yeah through the setup that is documented here (nothing about this changes really), for simplicity I'd just say we support this though and keep to a single setup (they are sadly mutually exclusive)
mydea
marked this pull request as ready for review
September 21, 2026 11:37
mydea
requested review from
JPeer264,
isaacs,
nicohrubec and
s1gr1d
and removed request for
a team
September 21, 2026 11:37
6 tasks
JPeer264
approved these changes
Sep 21, 2026
eve 0.62/0.63 changed its instrumentation contract: a flat
`agent/instrumentation.ts` is no longer discovered (it must live under
`agent/instrumentation/<provider>.ts` and export `defineInstrumentation(...)`),
and eve now stamps every AI SDK call with `recordInputs`/`recordOutputs: false`.
That per-call flag on the `ai:telemetry` channel outranks the global
`dataCollection.genAI` setting, so gen_ai message content was silently dropped.
Add two APIs (in `@sentry/server-utils`, re-exported from the runtime packages):
- `eveIntegration()` marks the client so the Vercel AI channel subscriber records
gen_ai inputs/outputs by default under eve; an explicit `dataCollection.genAI`
or `vercelAIIntegration({ recordInputs })` still take precedence.
- `Sentry.eveInstrumentation(options)` (in `@sentry/node`) is an all-in-one
provider for a single `agent/instrumentation/*.ts` file: it runs `Sentry.init`
(adding `eveIntegration`) at startup and tags each turn's AI spans with the eve
session id as the conversation id via `turn.started` / `step.attempt.started`
events, replacing the separate `eveConversationHook` file. Accepts
`getConversationId` to customize the id.
Also migrate the `node-eve` e2e app to eve `^0.63.0` and the new single-file
setup.
Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
…ages The `consistentExports` check requires packages that re-export `@sentry/node` by name (astro, bun, aws-serverless, google-cloud-serverless) to mirror its exports; add `eveInstrumentation` to each. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
Co-authored-by: Jan Peer Stöcklmair <jan.oster94@gmail.com>
mydea
force-pushed
the
feat/eve-instrumentation
branch
from
September 21, 2026 12:23
8027315 to
70f41cb
Compare
mydea
enabled auto-merge (squash)
September 21, 2026 12:24
47 tasks
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
2 participants
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.
eve 0.62/0.63 changed its instrumentation contract in two ways that broke the
node-evee2e app and made gen_ai content capture awkward: a flatagent/instrumentation.tsis no longer discovered (it must live underagent/instrumentation/<provider>.tsand exportdefineInstrumentation(...)), and eve now stamps every AI SDK call withrecordInputs/recordOutputs: false. That per-call flag on theai:telemetrychannel outranks the globaldataCollection.genAIsetting, so gen_ai message content was silently dropped — the only escape was settingrecordInputs/recordOutputsper integration, which is poor DX.This adds two APIs in
@sentry/server-utils, re-exported from the runtime packages:eveIntegration()— marks the client so the Vercel AI channel subscriber records gen_ai inputs/outputs by default under eve. An explicitdataCollection.genAIorvercelAIIntegration({ recordInputs })still take precedence.Sentry.eveInstrumentation(options)(in@sentry/node) — an all-in-one provider for a singleagent/instrumentation/*.tsfile. It runsSentry.init(addingeveIntegration) at server startup and tags each turn's AI spans with the eve session id as the Sentry conversation id viaturn.started/step.attempt.startedevents, replacing the separateeveConversationHookfile. AcceptsgetConversationIdto customize the id.The
node-evee2e app is migrated to eve^0.63.0and the new single-file setup.New Usage