# Kibana \[SOLVED\] Filter Applies to Incorrect Index: Visualize: failed to find geo\_point field \[nginxgeo1\]

**URL:** <https://discuss.elastic.co/t/kibana-solved-filter-applies-to-incorrect-index-visualize-failed-to-find-geo-point-field-nginxgeo1/84298>\
**Category:** Kibana\
**Created:** [May 2, 2017, 4:50pm UTC](https://discuss.elastic.co/t/kibana-solved-filter-applies-to-incorrect-index-visualize-failed-to-find-geo-point-field-nginxgeo1/84298 "2017-05-02T16:50:30Z")\
**Posts on this page:** 6\
**Page:** 1

<div class="post-metadata">

**Author:** ![seth.yes](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/seth.yes/32/11788_2.png) [@seth.yes](https://discuss.elastic.co/u/seth.yes)\
**Post date:** [May 2, 2017, 4:50pm UTC](https://discuss.elastic.co/t/kibana-solved-filter-applies-to-incorrect-index-visualize-failed-to-find-geo-point-field-nginxgeo1/84298/1 "2017-05-02T16:50:30Z")

</div>

I'm geomapping some data, all of which is located on my nginx index (e.g. nginx-2017.05.01) which contains the geo\_point; nginxgeo1.

However I'm receiving an error that Elasticsearch can't find the geo\_point field nginxgeo1 in the logstash index; logstash-2017.05.01. I of course do have a logstash index, but no data on this dashboard is being populated by the logstash index. Regardless, I still get this error:

```auto
Error: Request to Elasticsearch failed: {"error":{"root_cause":[{"type":"query_shard_exception","reason":"failed to find geo_point field [nginxgeo1]","index_uuid":"g6Uj2Qg3SialK4tqxccIyw","index":"logstash-2017.05.01"},{"type":"query_shard_exception","reason":"failed to find geo_point field [nginxgeo1]","index_uuid":"eN_0ify2RFO811SLs3iWrA","index":"logstash-2017.05.02"}],"type":"search_phase_execution_exception","reason":"all shards failed","phase":"query","grouped":true,"failed_shards":[{"shard":0,"index":"logstash-2017.05.01","node":"aC2_igyIQPivgRcTNEaMCQ","reason":{"type":"query_shard_exception","reason":"failed to find geo_point field [nginxgeo1]","index_uuid":"g6Uj2Qg3SialK4tqxccIyw","index":"logstash-2017.05.01"}},{"shard":0,"index":"logstash-2017.05.02","node":"x-ghbSl5Rf6ObX50KRY4DQ","reason":{"type":"query_shard_exception","reason":"failed to find geo_point field [nginxgeo1]","index_uuid":"eN_0ify2RFO811SLs3iWrA","index":"logstash-2017.05.02"}}],"caused_by":{"type":"query_shard_exception","reason":"failed to find geo_point field [nginxgeo1]","index_uuid":"eN_0ify2RFO811SLs3iWrA","index":"logstash-2017.05.02"}},"status":400}
    at http://opuscache/bundles/kibana.bundle.js?v=14823:28:19338
    at Function.Promise.try (http://opuscache/bundles/commons.bundle.js?v=14823:75:22403)
    at http://opuscache/bundles/commons.bundle.js?v=14823:75:21773
    at Array.map (native)
    at Function.Promise.map (http://opuscache/bundles/commons.bundle.js?v=14823:75:21728)
    at callResponseHandlers (http://opuscache/bundles/kibana.bundle.js?v=14823:28:18950)
    at http://opuscache/bundles/kibana.bundle.js?v=14823:28:7080
    at processQueue (http://opuscache/bundles/commons.bundle.js?v=14823:38:23621)
    at http://opuscache/bundles/commons.bundle.js?v=14823:38:23888
    at Scope.$eval (http://opuscache/bundles/commons.bundle.js?v=14823:39:4619)

```

Yet I have confirmed that all 7 visualizations are pointed to data on the nginx index, the one markdown widget is of course connected to no index. Furthermore, the only visualization that should be even querying the geo\_point nginxgeo1 is the tilemap, which is properly populated.

What could be causing Kibana to query the incorrect index?

## **Update:** it appears to be the Kibana filter which is causing this issue.

 ![](https://us1.discourse-cdn.com/elastic/original/3X/0/7/07ec7128c25649dab27b66dd42305763693b500b.png)

The error toggles with adding/removing this geofilter.

The filter:

```auto
{
  "geo_bounding_box": {
    "nginxgeo1": {
      "bottom_right": {
        "lat": 35.7008015333603,
        "lon": -114.24146653153002
      },
      "top_left": {
        "lat": 36.633162103994366,
        "lon": -115.87568284012377
      }
    }
  }
}

```

---

<div class="post-metadata">

**Author:** ![Joe\_Fleming](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/joe_fleming/32/3561_2.png) [@Joe\_Fleming](https://discuss.elastic.co/u/Joe_Fleming)\
**Post date:** [May 3, 2017, 6:19pm UTC](https://discuss.elastic.co/t/kibana-solved-filter-applies-to-incorrect-index-visualize-failed-to-find-geo-point-field-nginxgeo1/84298/2 "2017-05-03T18:19:11Z")

</div>

Are you sure you have a `nginxgeo1` field in your logstash indices? If so, perhaps check your [field mappings](https://www.elastic.co/guide/en/elasticsearch/reference/current/indices-get-field-mapping.html) and make sure Elasticsearch thinks that field is a `geo_point` type.

---

<div class="post-metadata">

**Author:** ![seth.yes](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/seth.yes/32/11788_2.png) [@seth.yes](https://discuss.elastic.co/u/seth.yes)\
**Post date:** [May 4, 2017, 3:17pm UTC](https://discuss.elastic.co/t/kibana-solved-filter-applies-to-incorrect-index-visualize-failed-to-find-geo-point-field-nginxgeo1/84298/3 "2017-05-04T15:17:21Z")

</div>

I must not be clearly communicating the issue.

### I do not have a field named nginxgeo1 in my logstash index, never have. Nor do I call on nginxgeo1 from any visualization other than the tilemap, which is pointed to the nginx index, which _does_ have the expected geo\_point field and displays properly.

The issue is that Kibana for some reason is expecting the geo\_point field to appear under the logstash index, however nothing I've configured in Kibana tells it to look for _any_ geo\_point field in the logstash index.

Does that make sense?

---

<div class="post-metadata">

**Author:** ![seth.yes](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/seth.yes/32/11788_2.png) [@seth.yes](https://discuss.elastic.co/u/seth.yes)\
**Post date:** [May 5, 2017, 4:34pm UTC](https://discuss.elastic.co/t/kibana-solved-filter-applies-to-incorrect-index-visualize-failed-to-find-geo-point-field-nginxgeo1/84298/4 "2017-05-05T16:34:54Z")

</div>

Found a workaround and posted it here: [[SOLVED] Kibana Geo Filter: Add Filter for Index](https://discuss.elastic.co/t/kibana-geo-filter-add-filter-for-index/84757/2)

---

<div class="post-metadata">

**Author:** ![Joe\_Fleming](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/joe_fleming/32/3561_2.png) [@Joe\_Fleming](https://discuss.elastic.co/u/Joe_Fleming)\
**Post date:** [May 10, 2017, 6:01pm UTC](https://discuss.elastic.co/t/kibana-solved-filter-applies-to-incorrect-index-visualize-failed-to-find-geo-point-field-nginxgeo1/84298/5 "2017-05-10T18:01:30Z")

</div>

Thanks for following up. I'll do you the same kindness. This was actually fixed recently, [in this PR](https://github.com/elastic/kibana/pull/11461), and the fix will ship in 5.5.0. I'm checking with the author to see if that should be backported too.

UPDATE: It's been backported, and will be included in 5.4.1.

---

<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:** [June 7, 2017, 6:07pm UTC](https://discuss.elastic.co/t/kibana-solved-filter-applies-to-incorrect-index-visualize-failed-to-find-geo-point-field-nginxgeo1/84298/6 "2017-06-07T18:07:23Z")

</div>

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