docs: list Sentry among OTel-compatible instrumentation backends - #2913
docs: list Sentry among OTel-compatible instrumentation backends#2913sergical wants to merge 2 commits into
Conversation
|
@sergical is attempting to deploy a commit to the Vercel Team on Vercel. A member of the Team first needs to authorize it. |
Signed-off-by: Sergiy Dybskiy <sergiy.dybskiy@sentry.io>
8b93551 to
61fc436
Compare
![vercel[bot]](https://avatars.githubusercontent.com/in/8329?s=60&v=4){kind=small}
| | +-- ai.toolCall {toolName: read} | ||
| +-- ai.streamText step 3 (final text) | ||
| +-- invoke_agent <agent> gen_ai.operation.name=invoke_agent | ||
| +-- step 1 gen_ai.operation.name=agent_step |
There was a problem hiding this comment.
The trace-hierarchy diagram claims the per-step span carries gen_ai.operation.name=agent_step, an attribute/value that eve never emits.
There was a problem hiding this comment.
This section documents the setup path, where eve creates ai.eve.turn (runtime.ts#L298) and hands telemetry to the AI SDK. On that path the step span comes from @ai-sdk/otel, not from eve. At the version eve pins (1.0.58), the integration sets gen_ai.operation.name: 'agent_step' (open-telemetry.ts#L648) and names the span step ${n} (open-telemetry.ts#L663).
eve's own provider in tracing/agent-otel-provider.ts emits no step spans, but that provider is not active in this hierarchy. I added a sentence that says which path the tree describes.
61fc436 to
7e6825c
Compare
| | +-- ai.streamText.doStream | ||
| | +-- ai.toolCall {toolName: read} | ||
| +-- ai.streamText step 3 (final text) | ||
| +-- invoke_agent <model> gen_ai.operation.name=invoke_agent |
There was a problem hiding this comment.
Docs incorrectly claim the invoke_agent span is named after the model and that gen_ai.agent.name holds a different value; both the diagram (invoke_agent <model>) and the prose are wrong.
There was a problem hiding this comment.
Same split. eve's provider names the span invoke_agent <agentName> (agent-otel-provider.ts#L677). The AI SDK integration names it ${operationName} ${event.modelId} (open-telemetry.ts#L305) and puts the agent name on gen_ai.agent.name from telemetry.functionId (open-telemetry.ts#L275), which eve defaults to the agent name (runtime.ts#L291).
I verified the resulting span name invoke_agent anthropic/claude-sonnet-5 in a trace exported from eve 0.49. The added sentence covers the provider case.
The AI SDK OpenTelemetry integration emits invoke_agent, agent_step, chat, and execute_tool spans. The guide still listed the legacy ai.streamText and ai.toolCall names. Signed-off-by: Sergiy Dybskiy <sergiy.dybskiy@sentry.io>
7e6825c to
464f2a6
Compare
1 participant
Summary
The instrumentation guide names the OTel-compatible backends eve works with and links the PostHog integration, but it does not mention Sentry, even though eve ships a Sentry instrumentation in its registry (
eve add instrumentation/sentry, documented at/integrations/sentry-instrumentation).This adds Sentry to the backend list in the OpenTelemetry section, links the Sentry integration page next to the PostHog one, and adds Sentry to the list of third-party backends in the workflow run tags section.
It also updates the "Authored trace hierarchy" tree. eve registers the AI SDK's
OpenTelemetryintegration, which emits GenAI semantic-convention spans (invoke_agent <model>,step N,chat <model>,execute_tool <tool>). The guide still showed the legacyai.streamTextandai.toolCallnames, which no longer appear in exported traces. Verified against a live trace exported to Sentry from eve 0.49.Docs-only change, no changeset.
Created with Claude Code