|
@@ -1,20 +1,17 @@
|
|
|
[[ingest-geoip]]
|
|
|
-=== Ingest Geoip Processor Plugin
|
|
|
+=== Ingest Geoip Processor
|
|
|
|
|
|
The GeoIP processor adds information about the geographical location of IP addresses, based on data from the Maxmind databases.
|
|
|
This processor adds this information by default under the `geoip` field. The `geoip` processor can resolve both IPv4 and
|
|
|
IPv6 addresses.
|
|
|
|
|
|
-The ingest-geoip plugin ships by default with the GeoLite2 City, GeoLite2 Country and GeoLite2 ASN geoip2 databases from Maxmind made available
|
|
|
+The ingest-geoip module ships by default with the GeoLite2 City, GeoLite2 Country and GeoLite2 ASN geoip2 databases from Maxmind made available
|
|
|
under the CCA-ShareAlike 4.0 license. For more details see, http://dev.maxmind.com/geoip/geoip2/geolite2/
|
|
|
|
|
|
The GeoIP processor can run with other geoip2 databases from Maxmind. The files must be copied into the geoip config directory,
|
|
|
and the `database_file` option should be used to specify the filename of the custom database. Custom database files must be stored
|
|
|
uncompressed. The geoip config directory is located at `$ES_HOME/config/ingest-geoip` and holds the shipped databases too.
|
|
|
|
|
|
-:plugin_name: ingest-geoip
|
|
|
-include::install_remove.asciidoc[]
|
|
|
-
|
|
|
[[using-ingest-geoip]]
|
|
|
==== Using the Geoip Processor in a Pipeline
|
|
|
|
|
@@ -25,7 +22,7 @@ include::install_remove.asciidoc[]
|
|
|
| Name | Required | Default | Description
|
|
|
| `field` | yes | - | The field to get the ip address from for the geographical lookup.
|
|
|
| `target_field` | no | geoip | The field that will hold the geographical information looked up from the Maxmind database.
|
|
|
-| `database_file` | no | GeoLite2-City.mmdb | The database filename in the geoip config directory. The ingest-geoip plugin ships with the GeoLite2-City.mmdb, GeoLite2-Country.mmdb and GeoLite2-ASN.mmdb files.
|
|
|
+| `database_file` | no | GeoLite2-City.mmdb | The database filename in the geoip config directory. The ingest-geoip module ships with the GeoLite2-City.mmdb, GeoLite2-Country.mmdb and GeoLite2-ASN.mmdb files.
|
|
|
| `properties` | no | [`continent_name`, `country_iso_code`, `region_iso_code`, `region_name`, `city_name`, `location`] * | Controls what properties are added to the `target_field` based on the geoip lookup.
|
|
|
| `ignore_missing` | no | `false` | If `true` and `field` does not exist, the processor quietly exits without modifying the document
|
|
|
|======
|
|
@@ -91,7 +88,7 @@ Which returns:
|
|
|
|
|
|
Here is an example that uses the default country database and adds the
|
|
|
geographical information to the `geo` field based on the `ip` field`. Note that
|
|
|
-this database is included in the plugin download. So this:
|
|
|
+this database is included in the module. So this:
|
|
|
|
|
|
[source,js]
|
|
|
--------------------------------------------------
|
|
@@ -190,7 +187,7 @@ Which returns:
|
|
|
|
|
|
[[ingest-geoip-mappings-note]]
|
|
|
===== Recognizing Location as a Geopoint
|
|
|
-Although this plugin enriches your document with a `location` field containing
|
|
|
+Although this processor enriches your document with a `location` field containing
|
|
|
the estimated latitude and longitude of the IP address, this field will not be
|
|
|
indexed as a {ref}/geo-point.html[`geo_point`] type in Elasticsearch without explicitely defining it
|
|
|
as such in the mapping.
|