2016-01-25 15:06:39 -05:00
[[ingest-geoip]]
2016-02-11 20:40:32 -05:00
=== Ingest Geoip Processor Plugin
2016-01-25 15:06:39 -05:00
The GeoIP processor adds information about the geographical location of IP addresses, based on data from the Maxmind databases.
2016-09-28 04:03:43 -04:00
This processor adds this information by default under the `geoip` field. The `geoip` processor can resolve both IPv4 and
IPv6 addresses.
2016-01-25 15:06:39 -05:00
2016-01-26 08:52:40 -05:00
The ingest-geoip plugin ships by default with the GeoLite2 City and GeoLite2 Country geoip2 databases from Maxmind made available
2016-01-25 15:06:39 -05:00
under the CCA-ShareAlike 3.0 license. For more details see, http://dev.maxmind.com/geoip/geoip2/geolite2/
2016-03-04 01:49:31 -05:00
The GeoIP processor can run with other geoip2 databases from Maxmind. The files must be copied into the geoip config directory,
2016-06-08 10:18:42 -04:00
and the `database_file` option should be used to specify the filename of the custom database. Custom database files must be compressed
with gzip. The geoip config directory is located at `$ES_HOME/config/ingest/geoip` and holds the shipped databases too.
2016-01-25 15:06:39 -05:00
2016-06-08 15:55:59 -04:00
[[ingest-geoip-install]]
[float]
==== Installation
This plugin can be installed using the plugin manager:
[source,sh]
----------------------------------------------------------------
sudo bin/elasticsearch-plugin install ingest-geoip
----------------------------------------------------------------
The plugin must be installed on every node in the cluster, and each node must
be restarted after installation.
2016-09-19 09:04:29 -04:00
This plugin can be downloaded for <<plugin-management-custom-url,offline install>> from
2016-10-07 13:17:10 -04:00
{plugin_url}/ingest-geoip/ingest-geoip-{version}.zip.
2016-09-12 09:34:44 -04:00
2016-06-08 15:55:59 -04:00
[[ingest-geoip-remove]]
[float]
==== Removal
The plugin can be removed with the following command:
[source,sh]
----------------------------------------------------------------
sudo bin/elasticsearch-plugin remove ingest-geoip
----------------------------------------------------------------
The node must be stopped before removing the plugin.
[[using-ingest-geoip]]
==== Using the Geoip Processor in a Pipeline
[[ingest-geoip-options]]
2016-01-25 15:06:39 -05:00
.Geoip options
[options="header"]
|======
| Name | Required | Default | Description
2016-04-20 12:00:11 -04:00
| `field` | yes | - | The field to get the ip address from for the geographical lookup.
2016-01-25 15:06:39 -05:00
| `target_field` | no | geoip | The field that will hold the geographical information looked up from the Maxmind database.
2016-06-08 10:18:42 -04:00
| `database_file` | no | GeoLite2-City.mmdb | The database filename in the geoip config directory. The ingest-geoip plugin ships with the GeoLite2-City.mmdb.gz and GeoLite2-Country.mmdb.gz files.
2016-04-20 12:00:11 -04:00
| `properties` | no | [`continent_name`, `country_iso_code`, `region_name`, `city_name`, `location`] * | Controls what properties are added to the `target_field` based on the geoip lookup.
2016-01-25 15:06:39 -05:00
|======
2016-02-11 20:40:32 -05:00
*Depends on what is available in `database_field`:
2016-03-04 01:49:31 -05:00
* If the GeoLite2 City database is used, then the following fields may be added under the `target_field`: `ip`,
2016-01-25 15:06:39 -05:00
`country_iso_code`, `country_name`, `continent_name`, `region_name`, `city_name`, `timezone`, `latitude`, `longitude`
2016-04-20 12:00:11 -04:00
and `location`. The fields actually added depend on what has been found and which properties were configured in `properties`.
2016-03-04 01:49:31 -05:00
* If the GeoLite2 Country database is used, then the following fields may be added under the `target_field`: `ip`,
2016-04-20 12:00:11 -04:00
`country_iso_code`, `country_name` and `continent_name`. The fields actually added depend on what has been found and which properties were configured in `properties`.
2016-01-25 15:06:39 -05:00
2016-03-04 01:49:31 -05:00
Here is an example that uses the default city database and adds the geographical information to the `geoip` field based on the `ip` field:
2016-01-25 15:06:39 -05:00
[source,js]
--------------------------------------------------
2016-08-10 08:55:42 -04:00
PUT _ingest/pipeline/geoip
2016-01-25 15:06:39 -05:00
{
2016-08-10 08:55:42 -04:00
"description" : "Add geoip info",
2016-01-25 15:06:39 -05:00
"processors" : [
{
"geoip" : {
2016-04-20 12:00:11 -04:00
"field" : "ip"
2016-01-25 15:06:39 -05:00
}
}
]
}
2016-08-10 08:55:42 -04:00
PUT my_index/my_type/my_id?pipeline=geoip
{
"ip": "8.8.8.8"
}
GET my_index/my_type/my_id
--------------------------------------------------
// CONSOLE
Which returns:
[source,js]
--------------------------------------------------
{
"found": true,
"_index": "my_index",
"_type": "my_type",
"_id": "my_id",
"_version": 1,
"_source": {
"ip": "8.8.8.8",
"geoip": {
"continent_name": "North America",
"country_iso_code": "US",
"region_name": "California",
"city_name": "Mountain View",
"location": { "lat": 37.386, "lon": -122.0838 }
}
}
}
2016-01-25 15:06:39 -05:00
--------------------------------------------------
2016-08-10 08:55:42 -04:00
// TESTRESPONSE
2016-01-25 15:06:39 -05:00
2016-08-10 08:55:42 -04:00
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:
2016-01-25 15:06:39 -05:00
[source,js]
--------------------------------------------------
2016-08-10 08:55:42 -04:00
PUT _ingest/pipeline/geoip
2016-01-25 15:06:39 -05:00
{
2016-08-10 08:55:42 -04:00
"description" : "Add geoip info",
2016-01-25 15:06:39 -05:00
"processors" : [
{
"geoip" : {
2016-04-20 12:00:11 -04:00
"field" : "ip",
2016-01-25 15:06:39 -05:00
"target_field" : "geo",
2016-08-10 08:55:42 -04:00
"database_file" : "GeoLite2-Country.mmdb.gz"
2016-01-25 15:06:39 -05:00
}
}
]
}
2016-08-10 08:55:42 -04:00
PUT my_index/my_type/my_id?pipeline=geoip
{
"ip": "8.8.8.8"
}
GET my_index/my_type/my_id
--------------------------------------------------
// CONSOLE
returns this:
[source,js]
--------------------------------------------------
{
"found": true,
"_index": "my_index",
"_type": "my_type",
"_id": "my_id",
"_version": 1,
"_source": {
"ip": "8.8.8.8",
"geo": {
"continent_name": "North America",
"country_iso_code": "US",
}
}
}
2016-01-25 15:06:39 -05:00
--------------------------------------------------
2016-08-10 08:55:42 -04:00
// TESTRESPONSE
2016-09-13 21:12:02 -04:00
Not all IP addresses find geo information from the database, When this
occurs, no `target_field` is inserted into the document.
Here is an example of what documents will be indexed as when information for "93.114.45.13"
cannot be found:
[source,js]
--------------------------------------------------
PUT _ingest/pipeline/geoip
{
"description" : "Add geoip info",
"processors" : [
{
"geoip" : {
"field" : "ip"
}
}
]
}
PUT my_index/my_type/my_id?pipeline=geoip
{
"ip": "93.114.45.13"
}
GET my_index/my_type/my_id
--------------------------------------------------
// CONSOLE
Which returns:
[source,js]
--------------------------------------------------
{
"found": true,
"_index": "my_index",
"_type": "my_type",
"_id": "my_id",
"_version": 1,
"_source": {
"ip": "93.114.45.13"
}
}
--------------------------------------------------
// TESTRESPONSE