Detection of IP addresses, geolocations, and user agents

Dynatrace automatically detects IP addresses, geolocations as well as browsers, devices, and operating systems.

IP addresses

IP addresses are automatically identified from the HTTP headers of web requests and the Dynatrace Real User Monitoring signal. However, when load balancers, CDNs, or proxies are used, the remote IP of the HTTP(S) request might be different from the original IP address from your end users' devices. For such cases, Dynatrace watches the HTTP headers most frequently used for identifying the originating IP address of a client connecting to a web server through an HTTP proxy, a CDN or a load balancer. To view which headers Dynatrace watches by default, go to Global Settings > Web & mobile monitoring -> IP determination. These headers are processed in a specific order. Dynatrace however allows you to change the processing order as well as to add your own headers.

Keep in mind that, by default, Dynatrace masks the last part of user device IP addresses.

Geolocations

Dynatrace Real User Monitoring tries to assign every user session a geolocation (city, region, country) in order to group user sessions and user actions per location and show them on the world map.

For web applications, Dynatrace uses the MaxMind Geo2 Database to map and resolve IP addresses to geographical locations.

For mobile apps, Dynatrace uses the coordinates from the device (GPS or wifi) if the app has the permission to use this information, and then Dynatrace calculates the city that is closest to the reported GPS location. If the mobile app doesn't have permissions to access geolocation information on the mobile operating system, it uses the IP address to determine the geolocation in combination again with the MaxMind Geo2 Database.

For custom locations using internal or private IP addresses, like for example your different offices, you can define custom IP mappings or even import a CSV file. You can even overwrite the default IP address mappings with custom IP address mapping rules.

Dynatrace by default also masks the GPS coordinates.

Browsers/Devices/Operating Systems

For web applications, distinguishing user sessions of real users from synthetic and robots is based on the user agent string sent by the browser. This string is used also for the identification of operating systems and device types like desktop, tablet, or mobile. For browsers classification, Dynatrace uses the www.udger.com user agent database. ISPs are detected based on the IP address. Dynatrace uses information provided by bgp.potaroo.net and www.cidr-report.org to identify the ISP for a given IP address.

Synthetic is only used for Dynatrace Synthetic monitoring, for example, browser monitors or the classic products (Gomez, Keynote, or AppMon synthetic).

Regarding mobile apps, device names are provided by Google Play Store for Android, while for iOS, Dynatrace maintains a cross reference list that maps Apple device IDs to Apple device names. The operating system—Android or iOS—is provided by Dynatrace OneAgent for mobile. As for web applications, ISPs are detected via a lookup of the user's device IP address in bgp.potaroo.net and www.cidr-report.org.