I've got UEM enabled on a website as well as AppMon. When I visit the site locally I can fill in a username and password, click "Login" and the username is successfully extracted and tied to a User Visit. When I'm connecting via a VPN (Juniper Network Connect) and I repeat the steps a purepath is created and I can see the user tag in the HTTP request but no user visit is generated. From answers to other questions I'm guessing that this is due to the PP being "orphaned" in some way. Please could someone suggest a value/variable/component which could be being blocked or mitigated by the VPN which would prevent the individual purepaths from being associated with a visit? Any help much appreciated!
I am not 100% sure but it seems to me like a X-Forward-For kind of issue.
Please have a look on the below link, if it works for you:
Also, can you use browser network tools to verify if the dtagent is being downloaded as you navigate through the App, and that the "Dynatrace Monitor" is not receiving a 300 or 400 error?
Hi Barbar, thanks I've validated that the UEM is active on the agent group and I can see an IP address so I believe the X-forwarding is working ok.
In the Web Server/Servlet/ASP.NET Sensor Properties, you can specify the "Request Header" with the value of "cookie". Once you are capturing the header, you can click on the top node (usually) in the PurePath that has the appropriate API and select details to the see the Request Header with the name "cookie" and make sure it has some "dt" cookies in it.