docs: add telemetry.dev instrumentation integration - #1325
Open
ephraimduncan wants to merge 3 commits into
Open
Conversation
Contributor
|
@ephraimduncan is attempting to deploy a commit to the Vercel Team on Vercel. A member of the Team first needs to authorize it. |
|
Review the following changes in direct dependencies. Learn more about Socket for GitHub.
|
Contributor
|
The latest updates on your projects. Learn more about Vercel for GitHub. |
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
1 participant
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.
Adds telemetry.dev as an instrumentation provider in the integrations directory and registry, installable with:
telemetry.dev is an observability platform for AI agents: OpenTelemetry traces for every model call, tool step, and turn, with tokens, cost, and latency attached.
Two supported setups
The integration page documents both, and either works:
eve addinstalls, following the Braintrust two-file pattern) — backed by the published@telemetry-dev/evepackage (peereve >=0.19.0 <1):agent/instrumentation.ts— registers telemetry.dev as the OpenTelemetry provider viatelemetryDevInstrumentation(), exporting eve's tracer scope and the AI SDK GenAI spans.agent/hooks/telemetry-dev.ts—telemetryDevHook()emits bounded lifecycle logs (session/turn/step, tool results, HITL, subagent and compaction events) joined to traces viagen_ai.conversation.id.@vercel/otel'sOTLPHttpProtoTraceExporterpointed athttps://ingest.telemetry.dev/v1/traceswith a Bearer header.Configuration is a single
TELEMETRY_DEV_API_KEYenv var for both.Changes
packages/eve-catalog: catalog entry (telemetry-dev, gallery only), placed before Jaeger so the local/self-hosted backend stays last.apps/docs/registry/instrumentation/telemetry-dev.ts+telemetry-dev-hook.ts: registry scaffolds.apps/docs/registry.json:instrumentation/telemetry-devitem with@telemetry-dev/evedependency andTELEMETRY_DEV_API_KEYenv var.apps/docs/scripts/validate-instrumentation-registry.ts: slug mapping and hook-file expectation (mirrors the Braintrust special case).apps/docs/lib/integrations/data.ts+logos.tsx: gallery presentation (both setup paths) and brand logo.apps/docs/package.json+ lockfile:@telemetry-dev/evedevDependency so the registry scaffolds typecheck.Validation
pnpm run registry:checkinapps/docspasses (shadcn build, connection/channel/instrumentation validators, registry tsc).pnpm run test:unitinapps/docs: 17/17 passing.oxfmt,oxlint, andsyncpack lintclean on touched files.