[nextjs] Handle more cases when auto-instrumenting tracing

[lobsterkatie]

There are a number of cases (some edge-case-y, some not) where we still don't fully support tracing in the nextjs SDK.

• Have spans for getInitialProps when run client-side
• Handle non-props responses from data-fetchers (redirects, etc)
• Add instrumentation for how long server-side rendering takes
• Support tracing when using a custom server (related: @sentry/nextjs and nextjs custom server #3782)
• Automatically wrap getStaticProps (Wrapper exists but we don't have access to the request. Is this solvable? Do we even care, given that this generally runs in the background?)
• Middleware support (this is a bigger conversation - tracked in Next.js middleware support #4206)

[ikryvorotenko]

is there an update on GetStaticProps? I can see it only needs some transaction creation logic.

Also, is there a workaround to make GetStaticProps instrumentation work? Like somehow passing the register an active transaction before GetStaticProps is called.

[lforst]

is there an update on GetStaticProps? I can see it only needs some transaction creation logic.

@ikryvorotenko Currently we don't have this on our short-term backlog. PRs welcome!

Also, is there a workaround to make GetStaticProps instrumentation work? Like somehow passing the register an active transaction before GetStaticProps is called.

You should just be able to start a transaction at the start of GSP and finish it at the end.

[AbhiPrasad]

@lforst Closing this issue - but lmk if we need to re-open.

[lforst]

@AbhiPrasad closing is fine! most of this is tracked elsewhere.