-
-
Notifications
You must be signed in to change notification settings - Fork 1.6k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
ref: Disable incoming HTTP request instrumentation #13918
ref: Disable incoming HTTP request instrumentation #13918
Conversation
@@ -56,7 +56,7 @@ test('Should record exceptions and transactions for faulty route handlers', asyn | |||
|
|||
expect(routehandlerTransaction.contexts?.trace?.status).toBe('internal_error'); | |||
expect(routehandlerTransaction.contexts?.trace?.op).toBe('http.server'); | |||
expect(routehandlerTransaction.contexts?.trace?.origin).toContain('auto.http.otel.http'); | |||
expect(routehandlerTransaction.contexts?.trace?.origin).toContain('auto'); |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This test keeps coming back 😄
size-limit report 📦
|
❌ 1 Tests Failed:
View the top 1 failed tests by shortest run time
To view individual test run time comparison to the main branch, go to the Test Analytics Dashboard |
} | ||
} | ||
|
||
// Next.js 13 is not correctly picking up tracing data for trace propagation so we use a back-fill strategy |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This is the worst thing I have done all week.
Disables the instrumentation for incoming HTTP requests to be consistent across Next.js versions for instrumentation.
Next 13 and 15 work with the HTTP instrumentation. 14 doesn't.