vercel__workflow/.changeset/event-write-stso-spans.md at codex/atomic-start-core

mirror of https://github.com/vercel/workflow.git synced 2026-09-14 19:59:43 +08:00

Files

T

Shalabh Chaturvedi 63cc09e24f feat(world-vercel): enrich STSO event spans (#3536 )

Enrich the existing v4 event-write `http POST` **CLIENT** span. No new
span is created.

The modified span is emitted by HTTP event writes through `fetchV4` /
`instrumentedFetch` and WebSocket event writes through the existing
synthetic parity span in `postEventFrameOverWs` / `withHttpClientSpan`.

## Added attributes

- `workflow.client.version` on every v4 event write, formatted as
`@workflow/world-vercel/<version>`
- `step.stso_ms` when the event input carries step-to-step overhead
telemetry
- `step.latency_optimizations` when the event input carries the active
runtime optimization list, such as `lazyStepStart`, `turbo`, and
`optimisticStart`

The span already inherits the client application OTEL `service.name` and
carries the event type, transport, URL, and status. The added fields
allow sampled STSO analysis by client service, Workflow SDK version, and
runtime mode on one span.

## Validation

- Dependency-aware `@workflow/world-vercel` build
- `ws-transport-spans.test.ts`: 13 tests passed
- `@workflow/world-vercel` typecheck
- Biome and `git diff --check`

---------

Co-authored-by: vercel[bot] <35613825+vercel[bot]@users.noreply.github.com>

2026-08-14 11:33:51 -07:00

209 B

Raw Permalink Blame History

@workflow/world-vercel

@workflow/world-vercel
patch

Add the Workflow client version, step-to-step overhead, and active latency optimizations to terminal event-write client spans for service and version latency analysis.

209 B Raw Permalink Blame History

209 B

Raw Permalink Blame History