feat(nitro): Instrument HTTP Server#19225
feat(nitro): Instrument HTTP Server#19225logaretm merged 32 commits intoawad/create-nitro-sdk-metadatafrom
Conversation
Codecov Results 📊Generated by Codecov Action |
Codecov Results 📊✅ 25 passed | ⏭️ 5 skipped | Total: 30 | Pass Rate: 83.33% | Execution Time: 13.58s All tests are passing successfully. Generated by Codecov Action |
size-limit report 📦
|
node-overhead report 🧳Note: This is a synthetic benchmark with a minimal express app and does not necessarily reflect the real-world performance impact in an application.
|
23a8b35 to
07ad5a1
Compare
81b555e to
161862d
Compare
c3fef9e to
6799854
Compare
a95e594 to
88d95df
Compare
1923dda to
be2f037
Compare
1317257 to
2a86160
Compare
3b30e36 to
36c96b6
Compare
|
This pull request has gone three weeks without activity. In another week, I will close it. But! If you comment or otherwise update it, I will reset the clock, and if you apply the label |
99ea611 to
9ded4c9
Compare
342ea3b to
8d44437
Compare
… hooks Replace otel-tracing-channel with @sentry/opentelemetry's vendored tracingChannel. Fix data.span -> data._sentrySpan references so tracing channel spans are actually ended. Export TracingChannelContextWithSpan type for consumers. Add e2e span nesting tests to verify context propagation through the full srvx -> h3 -> user code span tree. Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
0173b17 to
6b8d4d7
Compare
|
|
||
| await request.get('/api/non-existent-route'); | ||
|
|
||
| expect(errorReceived).toBe(false); |
There was a problem hiding this comment.
What we do in other e2e-tests for such tests is to have a separate flush endpoint that is called after the error endpoint to ensure that all events have been sent (e.g. nestjs, cloudflare), so I think it would be good to switch to that pattern here too
There was a problem hiding this comment.
Makes sense, I will merge this into the base branch but will make sure to do that! thanks!
4cd6415
into
awad/create-nitro-sdk-metadata
Implements HTTP server instrumentation for both `h3` and `srvx` by listening to their tracing channel events. - `h3` TC PR: h3js/h3#1251 - `srvx` TC PR: h3js/srvx#141 Closes #18123 --- **This PR is part of a stack:** - #20358 - #19224 - #19225 👈 - #19304 --------- Co-authored-by: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
Implements HTTP server instrumentation for both `h3` and `srvx` by listening to their tracing channel events. - `h3` TC PR: h3js/h3#1251 - `srvx` TC PR: h3js/srvx#141 Closes #18123 --- **This PR is part of a stack:** - #20358 - #19224 - #19225 👈 - #19304 --------- Co-authored-by: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
Implements HTTP server instrumentation for both
h3andsrvxby listening to their tracing channel events.h3TC PR: feat: experimental tracing support h3js/h3#1251srvxTC PR: feat: experimental tracing channel support h3js/srvx#141Closes #18123
This PR is part of a stack: