Skip to content
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
merged 1 commit into from
Oct 24, 2016

Conversation

monicasarbu
Copy link
Contributor

@monicasarbu monicasarbu commented Oct 18, 2016

Add client_geoip.location field of type geo_point to store the GeoIP information of the client_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 of client_location.

This change is required by #2793

@monicasarbu monicasarbu added the in progress Pull request is currently in progress. label Oct 18, 2016
@monicasarbu monicasarbu added review and removed in progress Pull request is currently in progress. labels 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
Copy link
Contributor

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.


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.
Copy link
Contributor

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.
@tsg tsg merged commit 17758fc into elastic:master Oct 24, 2016
@monicasarbu monicasarbu deleted the use_client_geoip branch November 4, 2016 15:05
@monicasarbu 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)
@tsg tsg removed the needs_backport PR is waiting to be backported to other branches. label Nov 4, 2016
tsg pushed a commit that referenced this pull request Nov 4, 2016
) (#2939)

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
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants