Working with Next.js RSC Error digests

[stephanie-anderson]

[lforst]

This needs upstream changes from React so we can work with it:

• Let us pass a custom digest or error ID of some sort that is propagated to the client.
• Let us determine the digest for an error on the server directly.

A sort-of workaround for this is proper distributed tracing which let's people approximate what errors correlate.

[lforst]

@steebchen No this issue is about being able to correlate Client errors caused by Server Component errors. My PR to Next.js should make this a bit easier at least: vercel/next.js#64256

If the SDK is not collecting backend errors for you, please open a new issue with reproduction steps. Thank you!

[lforst]

This is partially resolved by #12157 which will let you correlate client errors with their respective server component errors. I guess this is even better than the digest because the digest is a 1:1 mapping from client error to server error while technically the server could generate multiple errors.

I will close this issue to clean up our issue stream but we are in talks with the Vercel team to add an API to Next.js which would allow for the recording of the RSC Error digest on the server. This would likely come in the form of an onError hook in instrumentation.ts or similar.