-
Notifications
You must be signed in to change notification settings - Fork 9
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
Fix Next.js instrumentation #868
Comments
✔️ All good! |
Confirming that it's really broken. Let's see if we can find a quick win to make this work in some circumstances -- even if it it's something that isn't ideal, like downgrading Next.js. In the not-so-long term, it seems that the Next.js team are working on a built-in OpenTelemetry instrumentation. So eventually, supporting that and asking users to upgrade Next would be the way to go. It might be possible to backport some of that instrumentation, or take inspiration from it to fix this. |
Related issue https://github.com/appsignal/appsignal-docs/issues/1130 ? |
Next.js has a new release 13.2.0 with OpenTelemetry instrumentation. Let's use that. |
Updating here as well: waiting on some improvements to the Next.js OpenTelemetry instrumentation that are currently in progress. |
AppSignal for Node.js 3.0.14 was just released, which includes support for Next.js instrumentation via their newly-added, built-in OpenTelemetry support. It requires Next.js version 13.3.0 or above, and it is not compatible with the use of custom servers. Check out our Next.js integration documentation. |
I took a look at a Next.js application that Shairyar prepared (Slack conversation), instrumented with our Express documentation as described in the docs. We couldn't get it to report routing correctly — all requests end up logged as
GET
, even for requests to other endpoints usinggetServerSideProps
, which should be hitting the server.I think the Next.js instrumentation, at least in the way we suggest it’s set up in the docs, is likely broken.
To do
instrumentationHook
Next.js config option -- https://github.com/appsignal/appsignal-docs/pull/1258The text was updated successfully, but these errors were encountered: