How To
Summary
This solution is only appplicable to self-hosted backend in K8s. For self-hosted docker based, please refer GeoLite2 database docker-based.
Objective
In Self-hosted Backend k8s the eum-acceptor is able to collect the user browser information (including the IP). However, the Geography location can’t be determined by the IP.
Error typically in self-hosted k8s installation:
By enabling the EUM to capture GeoLocation data, the EUM accepter need to access Geographical location database.
Refer this link to download the geolite2-city.
Use the value of _ for user and the agent key for the password.
user: _
Password: $INSTANA_AGENT_KEY
Prerequisites
-
The
geoDbUrlmust be configured in CoreSpec. -
The values of the url must be hosted in a location that accessible. In our test scenario, we configurd a public accessible S3 buket.
e.g.
geoDbUrl: https://XXX-geodb.s3.eu-XXX-X.amazonaws.com/geolite2-city.tar.gz
Important
It is Important in production environment, that geodb is securely accessible by eum-acceptor.
Deployment Validation
Refer eum-acceptor log, the GeoIP using database found .. as below:
2022-10-25 09:29:28,529 INFO eum-acceptor com.instana.geoip.GeoIpService - Will provide GeoIP insights using database found at https://XXX-geodb.s3.eu-XXX-X.amazonaws.com/geolite2-city.tar.gz (http)
2022-10-25 09:29:29,129 INFO eum-acceptor org.reflections.Reflections - Reflections took xx ms to scan x urls, producing 3X keys and 9X values
The eum-processor should be able to translate the user location from the IP address. The user needs to reload the page, the Geographical the location would only be captured from point where the DB is downloaded.
Document Location
Worldwide
Was this topic helpful?
Document Information
Modified date:
08 August 2023
UID
ibm17000915