Set user for each incoming request on node server

[hannadrehman]

I was following this guide to identify users for sentry.
for any server application any incoming request needs to be authenticated, and post authentication we can identify user and set that scope in the sentry for example

await function authMiddleWare(req,res,next){
 //this is not an actual middleware. just an example
 const user = await getAuthUser(req);
 if(user){
  Sentry.configureScope(scope => scope.setUser(user.username));
 }
 next()
}

since nodejs is a single threaded runtime. its possible that multiple incoming requests can set user scope. i am not able to understand how will sentry keep this user context for the entire request, and log any issue for that particular user. when in reality its possible that the scope was overridden by some other request/user which can come in parallel.

fyi i am trying to integrate sentry in my remix-run application

[sneko]

Didn't try it but I guess instead of polluting the global scope you could try to set this at the time of sending the exception:

function authMiddleWare(req, res, next) {
    try {
        next()
    } catch (err) {
        const user = extractUserFromReq(req);
        
        Sentry.captureException(err, {
            user: user,
        });

        throw err;
    }
}

[AbhiPrasad]

Please refer to https://docs.sentry.io/platforms/node/configuration/async-context/ for how to set up async context isolation with the sentry sdk!

The remix SDK and nextjs SDK uses this under the hood to do isolation

[sneko]

@AbhiPrasad ok I was not aware of this thank you. Any idea for Next.js to set the user according to requests? See #8777