Splunk Search

updating geolocation DB

wainwrid
Engager

Currently, we are running 6.6.2 and are using the geolite2 DB to do the iplocation mapping.

I have read the following articles:

https://www.splunk.com/blog/2014/07/22/updating-the-iplocation-db.html

http://www.georgestarcher.com/splunk-updating-the-geoip-database/

However, maxmind states that this DB is End of Life'd. There will be no additional updates after next month.

https://support.maxmind.com/geolite-legacy-discontinuation-notice/

How is Splunk going to handle these lookups in the future? What method of updating will be done?

We have been debating creating a lookup table that utilizes BGP routes. Is there a best practice or built in functionality that accomplishes this already?

We looked at ASNGenerator, but this also relies on the End of Life data from maxmind.

0 Karma

richgalloway
SplunkTrust
SplunkTrust

Maxmind is ending the old GeoLite database. Splunk uses GeoLite2, which is not going away.

---
If this reply helps you, Karma would be appreciated.
Got questions? Get answers!

Join the Splunk Community Slack to learn, troubleshoot, and make connections with fellow Splunk practitioners in real time!

Meet up IRL or virtually!

Join Splunk User Groups to connect and learn in-person by region or remotely by topic or industry.

Get Updates on the Splunk Community!

From Data to Insight: Announcing the Winners of the Splunk Dashboard Contest

Hi Splunkers, First off, thank you to everyone who participated in our very first From Data to Insight: The ...

Splunk Developers: Construct Your Future at the .conf26 Builder Bar

Calling all Splunk architects, platform admins, and app developers: the site is open, and the blueprints are ...

Quick connection discovery mode for forwarders

When a Splunk forwarder loses connectivity to its indexers, it does not always reconnect immediately. In many ...