Custom geographic details
Instana maps end-user IP addresses to geographic details, e.g., city and country names. This is done by inspecting various HTTP headers to retrieve the end-user IP addresses. These IP addresses are then translated to geographic details with the help of Maxmind's geographic databases.
This page describes how to configure custom mapping rules from IP address ranges to geographic details. The main use case for these custom mapping rules are private networks. For example, when accessing (self-hosted) Instana installations through private networks. In such cases, public geographic databases will never contain relevant information and as such the translation process will provide either no results or only wrong/unhelpful results.
For self-hosted Instana installations, make sure that the configurations for end-user monitoring are completed.
Data format
Configuration through the Web REST API
Get configuration
curl -H "Authorization: apiToken $API_TOKEN" \
-H "Accept: text/csv" \
"https://$UNIT-$TENANT.instana.io/api/mobile-app-monitoring/config/$MOBILE_APP_ID/geo-mapping-rules"
Set configuration
curl -X PUT \
-H "Authorization: apiToken $API_TOKEN" \
-H "Accept: text/csv, application/json" \
-H "Content-Type: text/csv" \
"https://$UNIT-$TENANT.instana.io/api/mobile-app-monitoring/config/$MOBILE_APP_ID/geo-mapping-rules" \
-d 'network,latitude,longitude,accuracy_radius,city_name,subdivision_1_name,subdivision_1_iso_code,subdivision_2_name,subdivision_2_iso_code,country_name,country_iso_code,continent_name,continent_code
84.119.41.64/26,51.5900204,6.1974817,8,Kevelaer,North Rhine-Westphalia,NW,Kreis Kleve,KLE,Germany,DE,Europe,EU'