12 Oct 2023 01:39 PM - last edited on 24 Nov 2023 12:36 PM by Michal_Gebacki
Due to network NAT'ing, user IP is not available in our organizations RUM monitoring. I know there are various request headers evaluated and how the mapping of IPs to geolocation occur. I also understand the monitored application can capture information and send headers in requests. I was wondering if anyone has tried to alter the Dynatrace browser javascript agent to capture additional data, like the user IP, and send a custom header with this address when sending RUM data/beacon signals?
27 Nov 2023 01:21 PM
We use a hosted solution for proxy & NAT'ing that doesn't set the headers as expected. Essentially 'x-Forwarded-for' is being set to the proxy address, not the actual client. Looking for options to set a custom header to better geo-locate our private & public IP clients.