-
-
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
Next.js 13 app dir API route handlers #7228
Comments
As a temporary fix, I'm looking at using wrapApiHandlerWithSentry. Is it possible to use this with dynamic routes? |
@tomelliot Have you had luck getting |
@rsolomon sorry no progress to report |
Any update on this 🤔 |
It's simply not implemented yet. It's on our backlog. |
Released with |
thanks @AbhiPrasad, the new implementation helps a lot. assuming there is no need to wrap route handlers with |
@dmudro route handlers should be wrapped automatically as long as |
@lforst this isnt forking for me. I get all of my normal routes in my sentry performance tracing, but none of my api routes. Am I doing something wrong? I am using instrumentation.ts from the v8 migration docs and got tracing enabled in my sentry.client.ts |
@cyrus-za a lot has changed with Next.js itself and the SDK since we released support for this. Could you open a new GH issue and fill out the template? Thanks! |
This is solved for me. Turns out I had instrumentation.ts in the root rather than my src directory |
For future lurkers: If you have problems and stumble onto this issue, please open a new issue with reproduction steps! |
Problem Statement
Next.js released app dir route handlers: https://beta.nextjs.org/docs/routing/route-handlers
We should auto-instrument them.
Solution Brainstorm
We can add wrapper templates that wrap these files.
Stuff to consider:
The text was updated successfully, but these errors were encountered: