docs(research): plan traceWorkflowSpans for authored instrumentation - #1815
Draft
cmpadden wants to merge 1 commit into
Draft
docs(research): plan traceWorkflowSpans for authored instrumentation#1815cmpadden wants to merge 1 commit into
cmpadden wants to merge 1 commit into
Conversation
Signed-off-by: Colton Padden <colton.padden@vercel.com> Co-Authored-By: Colton Padden <colton.padden@vercel.com>
Contributor
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
cmpadden
marked this pull request as draft
August 7, 2026 19:48
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
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.
Summary
Related to #1779. Investigates whether
defineInstrumentationcan gain atraceWorkflowSpansoption and adds the research plan for it. No runtime change.instrumentations: []cannot suppress Workflow spans because they are created manually viatrace.getTracer("workflow")in@workflow/core,@workflow/world-local, and@workflow/world-vercel. eve also cannot reuse theAgentTraceSpanProcessortrick the issue cites: an authoredinstrumentation.tsowns the provider and the span processors, so eve has no export-time seam. The plan proposes the one interposition point eve does have — after the authoredsetupreturns, replace the delegate of the globalProxyTracerProviderwith a wrapper that returns a no-op tracer for theworkflowscope.Two things to weigh before implementing, both covered in the document alongside the rejected alternatives: this would be the first place eve mutates a tracer provider it does not own, and in the Workflow SDK's default
linkedtrace mode the run-origin span link lives on the span being suppressed.Validation
pnpm guard:invariants(covers research frontmatter)@vercel/otel+@opentelemetry/api: the global delegate swap is visible across module copies, Workflow packages resolve their tracer lazily so the swap lands first, and the exported topology keeps its trace id and re-parents agent spans onto the nearest surviving ancestor with no dangling parentsresearch/document onlyChecklist
CONTRIBUTING.mdevepackagegit commit --signoff)