# Geoip location not working - missing nginx.access.geoip.location

**URL:** https://discuss.elastic.co/t/geoip-location-not-working-missing-nginx-access-geoip-location/161723
**Category:** Beats
**Tags:** filebeat
**Created:** [December 20, 2018, 3:46pm UTC](https://discuss.elastic.co/t/geoip-location-not-working-missing-nginx-access-geoip-location/161723 "2018-12-20T15:46:51Z")
**Posts on this page:** 4
**Page:** 1

<div class="post-metadata">

### Author: ![c257dd0a514ccc788ecc](https://avatars.discourse-cdn.com/v4/letter/c/5e9695/32.png) [@c257dd0a514ccc788ecc](https://discuss.elastic.co/u/c257dd0a514ccc788ecc)
#### Post date: [December 20, 2018, 3:46pm UTC](https://discuss.elastic.co/t/geoip-location-not-working-missing-nginx-access-geoip-location/161723/1 "2018-12-20T15:46:52Z")

</div>

Hi. ELK stack version 6.5.4. I deployed a new server with nginx and I use Filebeat to send nginx logs the the elasticsearch cluster. I added the pluggin nginx and imported the dashboard (filebeat setup -e). The problem I have is that there is no nginx.access.geoip.location fields.

I have nginx.access.geoip.location.lat and nginx.access.geoip.location.lon.

Have I missed something ?

I received logstash nginx config from here: [https://www.elastic.co/guide/en/logstash/current/logstash-config-for-filebeat-modules.html#parsing-nginx](https://www.elastic.co/guide/en/logstash/current/logstash-config-for-filebeat-modules.html#parsing-nginx)

If open visualise tab - receive the error:

Saved object is missing  
Could not locate that index-pattern-field (id: geoip.location)

---

<div class="post-metadata">

### Author: ![jsoriano](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/jsoriano/32/27920_2.png) [@jsoriano](https://discuss.elastic.co/u/jsoriano)
#### Post date: [December 20, 2018, 5:24pm UTC](https://discuss.elastic.co/t/geoip-location-not-working-missing-nginx-access-geoip-location/161723/2 "2018-12-20T17:24:05Z")

</div>

Hi @c257dd0a514ccc788ecc,

Yes, it is expected that `nginx.access.geoip.location.lat` and `nginx.access.geoip.location.lon` fields exist, but not `nginx.access.geoip.location` or `geoip.location`.

Instead of using logstash to enrich the events you can setup the ingest pipelines included in the filebeat modules, for that, run `filebeat setup` from a node with direct access to elasticsearch and the nginx module enabled.

Btw, do you need to use logstash? If you are using it for parsing the logs you can also do it just with elasticsearch and filebeat modules.

Regarding this error `Could not locate that index-pattern-field (id: geoip.location)`, when do you see it? In the provided dashboard the `geoip.location` field is not being used.

---

<div class="post-metadata">

### Author: ![c257dd0a514ccc788ecc](https://avatars.discourse-cdn.com/v4/letter/c/5e9695/32.png) [@c257dd0a514ccc788ecc](https://discuss.elastic.co/u/c257dd0a514ccc788ecc)
#### Post date: [December 20, 2018, 7:09pm UTC](https://discuss.elastic.co/t/geoip-location-not-working-missing-nginx-access-geoip-location/161723/3 "2018-12-20T19:09:28Z")

</div>

Thanks. I remove in filebeat.yml output to logstash and enable output to elasticsearch. All nginx dashboards - is worked.

---

<div class="post-metadata">

### Author: ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)
#### Post date: [January 17, 2019, 7:09pm UTC](https://discuss.elastic.co/t/geoip-location-not-working-missing-nginx-access-geoip-location/161723/4 "2019-01-17T19:09:41Z")

</div>

This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.
