Skip to content

docs: update instrumentation integrations for the provider layout - #2068

Closed
chadhietala wants to merge 1 commit into
mainfrom
docs/otel-integration-providers
Closed

chadhietala wants to merge 1 commit into
mainfrom
docs/otel-integration-providers

Conversation

@chadhietala

@chadhietala chadhietala commented Aug 13, 2026 •

Copy link
Copy Markdown
Contributor

Summary

Updates the instrumentation integration docs and registry scaffolding on eve.dev/integrations for the provider-directory layout (agent/instrumentation/<slug>.ts), replacing the legacy single-file defineInstrumentation({ setup: () => registerOTel(...) }) form.

The seven OTLP/OTel backends (PostHog, Sentry, Datadog, Honeycomb, Arize, Raindrop, Jaeger) now export an otelIntegration({ traceExporter }) destination from eve/instrumentation/otel. The framework folds all declared destinations into one pipeline at startup, so per-backend registerOTel/setup is no longer needed. PostHog's step.started distinct_id attribution and Arize's openinference.project.name resource attribute are dropped — the former is not expressible as a destination, and the latter belongs on otel(), not per-destination.

Braintrust is not OTel and stays on its own SDK helper (braintrustEveInstrumentation), simplified to the self-initializing form without initLogger/defineState/setup (pending braintrust-sdk PR #2363).

Registry install targets, the instrumentation registry validator, the integration-page docs presentations, and the install-integrations.mdx layout sentence are updated to the directory layout.

Note: The registry tsc check will fail until the Braintrust SDK PR ships and the braintrust dependency is bumped. This draft is not intended to merge before then.

Validation

  • pnpm --filter eve-docs run registry:validate:instrumentation — passes
  • pnpm --filter eve-docs run test:unit — 154 passed
  • pnpm docs:check — 82 files, 262 snippets, 82 mdx ok
  • node scripts/validate-public-registry-requirements.mjs — passes
  • pnpm lint, pnpm fmt — clean
  • tsc --project registry/tsconfig.json — fails on braintrust.ts only (expected, pending SDK fix(eve): avoid npm override conflict in web chat setup #2363)

Checklist

  • I linked an issue with prior discussion confirming this change is wanted
  • I ran the relevant checks from CONTRIBUTING.md
  • I added tests and documentation where relevant
  • I added a changeset if this touches the published eve package
  • DCO sign-off passes for every commit (git commit --signoff)

Rewrite the seven OTLP/OTel backends (PostHog, Sentry, Datadog, Honeycomb,
Arize, Raindrop, Jaeger) from the legacy single-file defineInstrumentation +
registerOTel setup form to otelIntegration destinations exported from
agent/instrumentation/<slug>.ts. Braintrust is simplified to use the SDK's
self-initializing form (pending braintrust-sdk PR #2363).

Registry install targets, the instrumentation registry validator, the docs
integration presentations, and the install-integrations layout sentence are
updated to the provider-directory layout.

Signed-off-by: Chad Hietala <chad.hietala@vercel.com>
@vercel

vercel Bot commented Aug 13, 2026 •

Copy link
Copy Markdown
Contributor

The latest updates on your projects. Learn more about Vercel for GitHub.

Project Deployment Actions Updated (UTC)
eve-docs Error Error Aug 13, 2026 7:30pm
eve-docs-4759 Error Error Aug 13, 2026 7:30pm
eve-pkg Ready Ready Preview Aug 13, 2026 7:30pm

@chadhietala chadhietala changed the title docs: move instrumentation integrations to otelIntegration destinations docs: switch instrumentation integrations to otelIntegration destinations Aug 13, 2026
@chadhietala chadhietala changed the title docs: switch instrumentation integrations to otelIntegration destinations docs: update instrumentation integrations for the provider layout Aug 13, 2026
});
},
}) as Parameters<typeof defineInstrumentation>[0],
recordInputs: true,

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

braintrustEveInstrumentation({ recordInputs, recordOutputs }) uses options that don't exist on the pinned braintrust@3.24.0 function signature, breaking the docs type-check build.

Fix on Vercel

This branch had an error being deployed

2 failed and 1 active deployments
Preview – eve-docs — 19b062ba Deployed Aug 13, 2026 by vercel[bot]
Preview – eve-docs-4759 — 19b062ba Deployed Aug 13, 2026 by vercel[bot]
Preview – eve-pkg — 19b062ba Deployed Aug 13, 2026 by vercel[bot]
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant