getsentry
[@sentry/nextjs] Allow using multiple Sentry projects (server-side + client-side) including source maps and releases
Problem Statement
We are using Sentry for a Nextjs codebase for a while now and one major issue we have is that client-side and server-side exceptions are lumped togehter into a single project. While on any client-side project you will almost always have a high level of noise that is out of your control (expections caused by browser extensions, bots, legacy browser, etc.), on the server-side any exception is probably something that we cand and should react to.
Therefore we wanted to set up 2 separate Sentry projects for client-side and server-side exceptions. Configuring the 2 seperate DSNs is not a problem with the separate configs.
However, from looking at the docs and the code I could not find any way to make sure that source maps would be uploaded and releases would be created for 2 seperate projects.
Solution Brainstorm
Is there maybe another way to achieve this that I could not find? Is this a feature request you would consider merging? Or do you have some other input on how to better seperate server- and client-side exceptions in a Nextjs codebase?
Thank you very much for looking into this.
We don't support this at the moment, since the SDK only creates a single instance of the Sentry Webpack Plugin under the hood. Great suggestion though, backlogging for now but PRs welcome if anyone wants to take a look!
Why was this issue closed?
While we think it would be helpful to solve this issue, we're busy with a lot of other tasks at the moment. Therefore, this issue is not a priority for us at this time. If you still want to see this resolved, please consider opening a PR for it - we're always happy to review them.
Please feel free to leave a comment if you think this issue should be reopened.
