-
Notifications
You must be signed in to change notification settings - Fork 25k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Update GeoIP processor documentation #71211
Conversation
Pinging @elastic/es-core-features (Team:Core/Features) |
Pinging @elastic/es-docs (Team:Docs) |
@elasticmachine update branch |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks @probakowski!
Maybe we should also explain how databases are selected after the section about using custom databases. (first managed databases, then if missing from config databases and if missing then default shipped databases)
@@ -60,9 +60,9 @@ | |||
|
|||
public static final boolean GEOIP_V2_FEATURE_FLAG_ENABLED = "true".equals(System.getProperty("es.geoip_v2_feature_flag_enabled")); | |||
|
|||
public static final Setting<TimeValue> POLL_INTERVAL_SETTING = Setting.timeSetting("geoip.downloader.poll.interval", | |||
public static final Setting<TimeValue> POLL_INTERVAL_SETTING = Setting.timeSetting("ingest.geoip.downloader.poll.interval", |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
👍
How often there will be a check for new databases. Defaults to `3d`, minimum is `1d` | ||
|
||
[[ingest-geoip-air-gapped]] | ||
==== Updating GeoIP databases in air-gapped environments |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Maybe we should both bundle file based updating of databases and using proxy/geoip tool in one section called: 'using custom databases'? Which is for use cases when custom databases are used or Elasticsearch is used in air-gapped environments. This will have 2 sections, one for updating databases via config directory (which replaces the third paragraph of geoip page) and one for setting up a http proxy.
Then the third paragraph in the geoip page can removed, which isn't that important for most folks, since they will be using the Elastic managed databases.
@@ -11,12 +11,15 @@ IPv6 addresses. | |||
The `ingest-geoip` module ships by default with the GeoLite2 City, GeoLite2 Country and GeoLite2 ASN GeoIP2 databases from Maxmind made available |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Maybe change this into: The geoip
processor runs by default with the GeoLite2 City, GeoLite2 Country and GeoLite2 ASN GeoIP2 databases automatically managed by Elastic from Maxmind under the CCA-ShareAlike 4.0 license.
After we have updated the |
Thanks @martijnvg! I'm working on a PR to document that API now. I should have something up shortly. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@probakowski @martijnvg I pushed a commit with some edits to these docs. That commit also includes docs for the GeoIP stats API. Please feel free to leave feedback or make direct changes.
|
||
`total_download_time`:: | ||
(integer) | ||
Total milliseconds spent downloading databases. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Total milliseconds spent downloading databases.
@probakowski Can you confirm this is milliseconds? It looks like it in the source, but I had a hard time teasing it out. Thanks!
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Yes, this is in milliseconds.
@@ -4,21 +4,20 @@ | |||
<titleabbrev>GeoIP</titleabbrev> | |||
++++ | |||
|
|||
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 |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I removed the sentence about the geoip
field. This is covered in the parameter docs below.
@elasticmachine update branch |
@elasticmachine update branch |
Thank you very much for the changes @jrodewig, they look great! |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
This PR adds documentation for GeoIPv2 auto-update feature. It also changes related settings names from geoip.downloader.* to ingest.geoip.downloader to have the same convention as current setting. Relates to elastic#68920 Co-authored-by: Elastic Machine <[email protected]> Co-authored-by: James Rodewig <[email protected]>
* Update GeoIP processor documentation (#71211) This PR adds documentation for GeoIPv2 auto-update feature. It also changes related settings names from geoip.downloader.* to ingest.geoip.downloader to have the same convention as current setting. Relates to #68920 Co-authored-by: Elastic Machine <[email protected]> Co-authored-by: James Rodewig <[email protected]>
This PR adds documentation for GeoIPv2 auto-update feature.
It also changes related settings names from
geoip.downloader.*
toingest.geoip.downloader
to have the same convention as current setting.Relates to #68920