AppMon captures the client IP address. For CDNs and load balancers, AppMon watches for the appropriate HTTP headers and converts this IP address to a geo location with a built in database. The IP address is determined as follows:
- http-requestheader field "rproxy_remote_address"
- http-requestheader field "True-Client-IP"
- http-requestheader field "X-Client-Ip"
- http-requestheader field "X-Forwarded-For"
- http-requestheader field "X-Http-Client-Ip"
- ip-address of requester
Locations may be assigned to internal IP addresses in the geographical locations section of the server settings. See Geographical Locations - Mapping of IP Addresses for more information. The geographical location is displayed in several dashlets. See Visits Dashlet, User Actions Dashlet, User Action PurePaths Dashlet and World Map Dashlet for more information.
Configuration - world map
The World Map data is based on business transactions Measures, whose grouping is by geographical location. To customize the desired level of detail within the World Map, select Edit map granularity from the context menu. The World Map dashlet uses out of the box measures, grouped by the Country of Visit Measure.
Measure Configuration Tab
Configure the desired geographical granularity by the Measure Properties dialog box shown. The following are available options for geographical granularity.
- Continent: Only the continent name is returned.
- Country: The result of the measure is the country name.
- Custom Regions: The result is either a country name or
<country name> - <region name>for all countries or continents listed in the Regions enabled for table.
Country and region names are taken from the internal geographical locations database using the ISO 3166-2 standard for the US and Canada, and the FIPS 10-4 standard for the rest of the world. The country is encoded using the ISO 3166-1 Alpha-2 country codes.