Backport: Use client_geoip.location for the GeoIP location of the client_ip #2939
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
…astic#2795) This information is available if you use the GeoIP processor from the Ingest GeoIP Processor Plugin. (cherry picked from commit 17758fc)
|
I have tested this feature manually, by following the steps from our docs, and it seems to work fine. cc-ed: @dedemorton |
leweafan
pushed a commit
to leweafan/beats
that referenced
this pull request
Apr 28, 2023
…astic#2795) (elastic#2939) This information is available if you use the GeoIP processor from the Ingest GeoIP Processor Plugin. (cherry picked from commit 742c48b)
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Backport of #2795:
This information is available if you use the GeoIP processor from the Ingest GeoIP Processor Plugin.
(cherry picked from commit 17758fc)