-
Notifications
You must be signed in to change notification settings - Fork 4.9k
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
Use client_geoip.location for the GeoIP location of the client_ip #2795
Merged
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
monicasarbu
added
review
and removed
in progress
Pull request is currently in progress.
labels
Oct 18, 2016
monicasarbu
force-pushed
the
use_client_geoip
branch
from
October 18, 2016 12:01
06ebc0e
to
ac5be70
Compare
tsg
reviewed
Oct 18, 2016
description: > | ||
The GeoIP locatio nof the `client_ip` address. This field is available | ||
only if you define a GeoIP Processor as a pipeline in the Ingest Geoip Processor Plugin | ||
(https://www.elastic.co/guide/en/elasticsearch/plugins/master/using-ingest-geoip.html) or |
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.
You can use asciidoc syntax for the links here.
monicasarbu
force-pushed
the
use_client_geoip
branch
from
October 18, 2016 13:24
0903081
to
6122b01
Compare
tsg
reviewed
Oct 18, 2016
|
||
example: {'lat': 51, 'lon': 9} | ||
|
||
The GeoIP locatio nof the `client_ip` address. This field is available only if you define a https://www.elastic.co/guide/en/elasticsearch/plugins/master/using-ingest-geoip.html[GeoIP Processor] as a pipeline in the https://www.elastic.co/guide/en/elasticsearch/plugins/master/ingest-geoip.html[Ingest GeoIP processor plugin] or using Logstash. |
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.
typo in locatio nof
This information is available if you use the GeoIP processor from the Ingest GeoIP Processor Plugin.
monicasarbu
force-pushed
the
use_client_geoip
branch
from
October 24, 2016 08:44
30099f4
to
6a0a9a9
Compare
monicasarbu
added
the
needs_backport
PR is waiting to be backported to other branches.
label
Nov 4, 2016
monicasarbu
added a commit
to monicasarbu/beats
that referenced
this pull request
Nov 4, 2016
…astic#2795) This information is available if you use the GeoIP processor from the Ingest GeoIP Processor Plugin. (cherry picked from commit 17758fc)
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.
Add
client_geoip.location
field of typegeo_point
to store the GeoIP information of theclient_ip
field. This information is available if you use the GeoIP processor from the Ingest GeoIP Processor Plugin.This PR also updates the Kibana dashboard for Packetbeat to use
client_geoip.location
instead ofclient_location
.This change is required by #2793