github-mirrors/elasticsearch
1
0
Fork 0
mirror of https://github.com/elastic/elasticsearch.git synced 2025-04-25 07:37:19 -04:00
Code Issues Projects Releases Packages Wiki Activity

Ingest geoip new databases release highlight (#109355)

Browse source
This commit is contained in:
Joe Gallo 2024-06-04 12:48:19 -04:00 • committed by GitHub
parent 6955427699
commit d9941f6285
No known key found for this signature in database
GPG key ID: B5690EEEBB952194
5 changed files with 16 additions and 68 deletions
Download patch file Download diff file Expand all files Collapse all files

8
docs/changelog/107377.yaml
View file

@ -3,3 +3,11 @@ summary: Add support for the 'Enterprise' database to the geoip processor
area: Ingest Node
type: enhancement
issues: []
highlight:
title: "Preview: Support for the 'Anonymous IP' and 'Enterprise' databases in the geoip processor"
body: |-
As a Technical Preview, the {ref}/geoip-processor.html[`geoip`] processor can now use the commercial
https://www.maxmind.com/en/solutions/geoip2-enterprise-product-suite/enterprise-database[GeoIP2 'Enterprise']
and
https://www.maxmind.com/en/solutions/geoip2-enterprise-product-suite/anonymous-ip-database[GeoIP2 'Anonymous IP']
databases from MaxMind.

23
docs/changelog/108639.yaml
View file

@ -3,26 +3,3 @@ summary: Add support for the 'Domain' database to the geoip processor
area: Ingest Node
type: enhancement
issues: []
highlight:
title: Add support for the 'Domain' database to the geoip processor
body: |-
Follow on to #107287 and #107377
Adds support for the ['GeoIP2
Domain'](https://dev.maxmind.com/geoip/docs/databases/domain) database
from MaxMind to the `geoip` processor.
The `geoip` processor will automatically download the [various
'GeoLite2'
databases](https://dev.maxmind.com/geoip/geolite2-free-geolocation-data),
but the 'GeoIP2 Domain' database is not a 'GeoLite2' database -- it's a
commercial database available to those with a suitable license from
MaxMind.
The support that is being added for it in this PR is in line with the
support that we already have for MaxMind's 'GeoIP2 City' and 'GeoIP2
Country' databases -- that is, one would need to arrange their own
download management via some custom endpoint or otherwise arrange for
the relevant file(s) to be in the `$ES_CONFIG/ingest-geoip` directory on
the nodes of the cluster.
notable: true

24
docs/changelog/108651.yaml
View file

@ -3,27 +3,3 @@ summary: Add support for the 'ISP' database to the geoip processor
area: Ingest Node
type: enhancement
issues: []
highlight:
title: Add support for the 'ISP' database to the geoip processor
body: |-
Follow on to https://github.com/elastic/elasticsearch/pull/107287,
https://github.com/elastic/elasticsearch/pull/107377, and
https://github.com/elastic/elasticsearch/pull/108639
Adds support for the ['GeoIP2
ISP'](https://dev.maxmind.com/geoip/docs/databases/isp) database from
MaxMind to the geoip processor.
The geoip processor will automatically download the [various 'GeoLite2'
databases](https://dev.maxmind.com/geoip/geolite2-free-geolocation-data),
but the 'GeoIP2 ISP' database is not a 'GeoLite2' database -- it's a
commercial database available to those with a suitable license from
MaxMind.
The support that is being added for it in this PR is in line with the
support that we already have for MaxMind's 'GeoIP2 City' and 'GeoIP2
Country' databases -- that is, one would need to arrange their own
download management via some custom endpoint or otherwise arrange for
the relevant file(s) to be in the $ES_CONFIG/ingest-geoip directory on
the nodes of the cluster.
notable: true

28
docs/changelog/108683.yaml
View file

@ -4,25 +4,11 @@ area: Ingest Node
type: enhancement
issues: []
highlight:
title: Add support for the 'Connection Type' database to the geoip processor
title: "Preview: Support for the 'Connection Type, 'Domain', and 'ISP' databases in the geoip processor"
body: |-
Follow on to #107287, #107377, #108639, and #108651
Adds support for the ['GeoIP2 Connection
Type'](https://dev.maxmind.com/geoip/docs/databases/connection-type)
database from MaxMind to the `geoip` processor.
The `geoip` processor will automatically download the [various
'GeoLite2'
databases](https://dev.maxmind.com/geoip/geolite2-free-geolocation-data),
but the 'GeoIP2 Connection Type' database is not a 'GeoLite2' database
-- it's a commercial database available to those with a suitable license
from MaxMind.
The support that is being added for it in this PR is in line with the
support that we already have for MaxMind's 'GeoIP2 City' and 'GeoIP2
Country' databases -- that is, one would need to arrange their own
download management via some custom endpoint or otherwise arrange for
the relevant file(s) to be in the `$ES_CONFIG/ingest-geoip` directory on
the nodes of the cluster.
notable: true
As a Technical Preview, the {ref}/geoip-processor.html[`geoip`] processor can now use the commercial
https://dev.maxmind.com/geoip/docs/databases/connection-type[GeoIP2 'Connection Type'],
https://dev.maxmind.com/geoip/docs/databases/domain[GeoIP2 'Domain'],
and
https://dev.maxmind.com/geoip/docs/databases/isp[GeoIP2 'ISP']
databases from MaxMind.

1
docs/reference/ingest/processors/geoip.asciidoc
View file

@ -72,6 +72,7 @@ depend on what has been found and which properties were configured in `propertie
`residential_proxy`, `domain`, `isp`, `isp_organization`, `mobile_country_code`, `mobile_network_code`, `user_type`, and
`connection_type`. The fields actually added depend on what has been found and which properties were configured in `properties`.
preview::["Do not use the GeoIP2 Anonymous IP, GeoIP2 Connection Type, GeoIP2 Domain, GeoIP2 ISP, and GeoIP2 Enterprise databases in production environments. This functionality is in technical preview and may be changed or removed in a future release. Elastic will work to fix any issues, but features in technical preview are not subject to the support SLA of official GA features."]
Here is an example that uses the default city database and adds the geographical information to the `geoip` field based on the `ip` field: