Description:
We propose adding an geoip function to OpenSearch's Piped Processing Language (PPL) and SQL to provide built-in IP address geolocation capabilities.
This feature would be similar to functionality used in OpenSearch's geospatial feature, enhancing PPL's ability to enrich log data with geographical information based on IP addresses.
Proposed Functionality:
The 'geoip' function should take an IP address as input and return geographical information.
It should support both IPv4 and IPv6 addresses.
The function should return multiple fields including country, region, city, latitude, longitude, and others as available.
It should allow users to specify which geolocation fields to include in the output.
The function should use a regularly updated IP geolocation database for accuracy.
Example Usage:
... | eval geolocation = geoip(ip_field)
This would add a new field 'geolocation' with all available location information for the IP address in 'ip_field'.
... | eval country = geoip(ip_field, "country")
... | eval lat = geoip(ip_field, "lat"), lon = iplocation(ip_field, "lon")
This would add new fields with specific geolocation information.
Description: We propose adding an
geoip
function to OpenSearch's Piped Processing Language (PPL) and SQL to provide built-in IP address geolocation capabilities. This feature would be similar to functionality used in OpenSearch's geospatial feature, enhancing PPL's ability to enrich log data with geographical information based on IP addresses.Proposed Functionality:
Example Usage:
This would add a new field 'geolocation' with all available location information for the IP address in 'ip_field'.
This would add new fields with specific geolocation information.
This would add a new field 'location_info' with multiple pieces of geolocation data.
Additional considerations