Custom geographic details

Instana maps end-user IP addresses to geographic details, for example, city and country names 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.

The Custom geographic details describe how to configure custom-mapping rules from IP address ranges to geographic details. The main use cases for these custom-mapping rules are private networks. For example, when you access self-hosted Instana installations through private networks. In such cases, public geographic databases never contains relevant information and as such the translation process provides either no results or only wrong or unhelpful results.

For self-hosted Instana installations, make sure that the configurations for end-user monitoring are completed.

Data format

See the corresponding section for website monitoring.

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'

Configuration through the user interface

See configuration through the user interface.