feat(tracing): add App response start spans - #3271
james-elicx wants to merge 1 commit into
Conversation
|
/bigbonk review for issues. You have an eight-minute time limit: report all concrete findings within eight minutes, prioritizing response stream lifecycle, Next.js startResponse parity, cache HIT/RSC representation handling, Workerd Response state, and Sentry/Workers tracing architecture. |
|
error: Your local changes to the following files would be overwritten by checkout: |
|
@james-elicx Bonk workflow failed. Check the logs for details. View workflow run · To retry, trigger Bonk again. |
@vinext/cloudflare
create-vinext-app
@vinext/types
vinext
@cloudflare/workers-response-store
commit: |
34f378e to
447a9ed
Compare
|
Performance benchmarksCompared 0 improved · 0 regressed · 6 within ±1.5%
View detailed results and traces 🟢 improvement · 🔴 regression · ⚫ change below 1.5% · paired base/head |
Summary
NextNodeServer.startResponseboundary for matched App Pages and Route Handlers through the shared framework tracer@sentry/nextjsfixture through real self-contained Response Store and a focused Workers Cache projectNo OpenTelemetry package becomes a vinext dependency, and there is no Sentry-specific framework tracing path.
Stack
Depends on #3270 (
feat(tracing): add App segment module spans).Validation
vp checkpnpm --filter @vinext/cloudflare test: 30 passed