Repository navigation
Conversation
Eve 0.62.0 removed agent/instrumentation.ts. The build fails when the file exists. The guide now puts Sentry.init in agent/instrumentation/sentry.ts with a default-exported provider. The guide also states that Eve turns off prompt and output recording outside development, shows the vercelAIIntegration options that turn it on, and warns against Eve's otel() providers next to the SDK setup. Co-authored-by: Claude <claude@anthropic.com>
|
The latest updates on your projects. Learn more about Vercel for GitHub.
1 Skipped Deployment
|
![sentry[bot]](https://avatars.githubusercontent.com/in/12637?s=60&v=4){kind=small}
| ```typescript {filename:agent/instrumentation/sentry.ts} | ||
| Sentry.init({ | ||
| dsn: "___PUBLIC_DSN___", | ||
| dataCollection: { |
There was a problem hiding this comment.
Bug: Documentation snippets for agent/instrumentation/sentry.ts are presented as complete files but lack the required export default defineInstrumentation({...}) wrapper, causing build failures.
Severity: MEDIUM
Suggested Fix
Update the documentation snippets to either include the full, valid file content including the export default defineInstrumentation({...}) wrapper and necessary imports, or explicitly label them as partial examples that must be merged into the existing file configuration. This will prevent users from creating invalid files.
Prompt for AI Agent
Review the code at the location below. A potential bug has been identified by an AI
agent. Verify if this is a real issue. If it is, propose a fix; if not, explain why it's
not valid.
Location: docs/platforms/javascript/guides/eve/index.mdx#L156-L159
Potential issue: The documentation for Eve presents several code snippets for
`agent/instrumentation/sentry.ts` as if they are complete files, using a filename
indicator. However, these snippets are missing the required `export default
defineInstrumentation({...})` wrapper. The guide explicitly states that every file in
the `agent/instrumentation/` directory must have this default export. A user copying and
pasting these incomplete snippets from sections like 'Privacy Controls' or 'Record
Prompts' will create an invalid file, causing the Eve build process to fail.
Also affects:
docs/platforms/javascript/guides/eve/index.mdx:173~183
Did we get this right? 👍 / 👎 to inform future reviews.
|
Closing. #19529 landed first and documents the new |
DESCRIBE YOUR PR
Eve
0.62.0removedagent/instrumentation.ts. When the file exists,eve buildfails with this error:The Eve guide still told users to create that file. A user who follows the guide on a current Eve version cannot build their agent.
Changes to
docs/platforms/javascript/guides/eve/index.mdx:Sentry.initmoves toagent/instrumentation/sentry.ts. Eve requires each file in that directory to default-export a provider, so the file exportsdefineInstrumentation({ flush }), which also flushes Sentry when Eve flushes telemetry.agent/instrumentation/is a provider, so helper code belongs in a different directory.eve dev. Outside development, Eve passesrecordInputs: falseandrecordOutputs: falseon each model call, and those values take priority overdataCollection.genAI. A new subsection shows the fix:Sentry.vercelAIIntegration({ recordInputs: true, recordOutputs: true }).otel()andotelIntegration()providers next to the SDK setup. Eve refuses to start when the global tracer provider is already registered.0.63.0.How I tested:
eve0.63.0with@sentry/node11.0.0-rc.0, two-turn sessions undereve devandeve start. I checked thegen_ai.*spans, the conversation id, and the recorded inputs and outputs in Sentry. The example app is in getsentry/sentry-agent-tracing-examples.IS YOUR CHANGE URGENT?
PRE-MERGE CHECKLIST
Created with Claude Code