As of now, you would have to call Sentry.setUser() in each server component individually. That is because server components are separated logically.

For the client you generally only have to set it once per pageload, so you can set it somewhere pretty high in a layout or something. And yes I would use useEffect for it. I do it like this in my side-project so that the user value gets updated when let's say somebody switches accounts:

useEffect(() => {
  Sentry.setUser({ id: userId })
}, [userId])

Thank you!

setUser sets the user on the current isolation scope. where this applies depends on where you call it - but in most cases in Next.js this should be on a per-route basis and not leak to other routes. Could you share a code snippet (with file path) of where/how you are using setUser in a place where it leaks for you?

At the beginning of any given page/route handler/server action, we do:

1. make async call to determine the user
2. call Sentry.setUser()

After that we execute the business logic, which involves multiple async calls typically. In general this works, but I have observed cases where a given Sentry issue has the wrong user set.

There's nothing particularly exotic about how we are calling it. A typical example would look like:

"use server";

export async function fooAction(...) {
  const session = await getSession();
  Sentry.setUser(session.user);
  const data = await getData(...);
  // some code which throws and triggers a sentry issue
}