The request attribute works on the server-side to capture the User ID/Name but the same is not working for the user tagging.
What could be the reason?
That does not seem to go to a RUM-enabled application. Your backtrace has only one node (the service which you started the backtrace). Hence why you're seeing "Requests to ..." but not "Requests from ...". Also, the last node of the backtrace (which needs to be a RUM-enabled application) needs to show User Actions.
Only User Actions are mapped to a User Session. So the problem is that the PurePaths where you are collecting User ID are not actually directly associated with any User Action of a RUM-enabled application and so it's impossible for us to use that attribute to tag sessions.
Here's a visual example:
Hi @Babar Q.
The request attribute is configured correctly, because we are capturing it. However I am unsure your application is monitored correctly.
You need to ensure the following:
If any of these steps don't work, you need to resolve it.
From what I can see, your backtrace didn't lead to an Application. So that's a good place to start understanding if you're monitoring your application correctly.
Then you've found your problem.
Unless Application is tied to Service which has Requests with the attribute, you cannot use that attribute to tag your sessions because we have no idea what sessions those requests belong to.
Possibly when you're going to instrument the web servers, and the RUM injection will be done directly via OneAgent, then your attribute can be used for tagging sessions.