Should Geo Server location work by default?

[CommunityUser]

I just installed Web EUM on a Windows-based on-premise installation.  We made the necessary updates to our application so the EUM data is flowing to the EUM dashboard and that all appears to work ok.  However, we are not getting any geolocation data.  The map of the world and the US are blank even though many transactions have flowed into EUM.  In reading the documentation on the Geo Server, it says:

By default, end-users' locations are resolved using public geographic databases. You can host an alternate geo server for your countries, regions, and cities instead of using the default geo server hosted by AppDynamics. Use the Geo Server URL field to point to your custom geo server.

So it sounds like this funcitonality should work out of the box without setting up a custom Geo Server, but it's not.  I assume this is related, but the location data in the Javascript request is null (screenshot attached). Does this work for anyone else?

[Venu_Babu_Thang]

Hi,

The countries and regions mentioned in the below document link are displayed in the geographic dashboard.  Each of these countries and regions also display their own aggregate EUEM data. Data can be collected from areas not in the mentioned list, but it will not be displayed in these parts of the interface.

https://docs.appdynamics.com/display/PRO40/Web+EUEM+Countries+and+Regions+by+Geo+Dashboard

If your location is not the list, then you would need to setup a custom geo server.

Please let me know if you have any further questions.

Thanks,

Venu.

[CommunityUser]

I ended up getting this working.  In talking to AD support they mentioned that the location data in the Javascript is not used for the geolocation data, rather it uses the IP address passed back to the server.  Our reverse proxy by default will strip off the IP addresses as they come in.  Per our infrastructure guy:

"In order to avoid an asymmetric routing condition, the Big IP replaces the client source IP address with its own IP address.  So, as far as source IP addresses, the EUEM will always see the internal address(es) of the Big IP.  However, we can enable the x-forwarded-for header in the HTTP profile, if the EUEM is able to use it."  

So I checked with AD support and they said it does support the x-forwarded-for header, so we enabled that, and once we did the geolocation functionality started working.