docs(research): instrumentation providers proposal - #1799
Open
chadhietala wants to merge 1 commit into
Open
Conversation
Contributor
|
The latest updates on your projects. Learn more about Vercel for GitHub.
1 Skipped Deployment
|
Documents the proposal to have eve own the OpenTelemetry pipeline and expose the lifecycle bus underneath it, so local tracing and Agent Runs stay on when an agent brings a backend of its own, and a backend that is not OpenTelemetry has a provider surface to build against. Signed-off-by: Chad Hietala <chadhietala@gmail.com>
chadhietala
force-pushed
the
research/instrumentation-providers
branch
from
August 7, 2026 17:23
982bfa1 to
a460da2
Compare
5 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
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
research/instrumentation-providers.md— the instrumentation providers proposal, written so it can be shared outside the repo for feedback (Braintrust in particular, since a non-OTel backend is the case the current surface serves worst).The problem. eve's one public observability extension point assumes OpenTelemetry. Authoring
agent/instrumentation.tscallsregisterOTel, which takes the process's single global tracer provider slot, so eve stops installing local tracing rather than collide with it. Two OTel backends in onesetupsilently exports from one of them. A backend that records rows rather than spans has no surface at all, so the Braintrust integration reconstructs execution from the runtime event stream — the protocol that renders a conversation.The proposal. eve owns the pipeline and exposes the lifecycle bus underneath it.
instrumentation/becomes a directory, one provider per file, the waytools/andhooks/already work. OTel is one provider on the bus and the only one that builds a tracer provider; its per-process singletons (instrumentation/otel.ts) split from its destinations (instrumentation/<backend>.ts). Local traces and Agent Runs stay on regardless, with two reserved filenames to disable or narrow them. Providers get durable per-operation state and a replay-stableidempotencyKey, which is what a row backend needs and currently hand-rolls.Docs-only; no changeset.
pnpm docs:checkpasses.