# Could not locate that index-pattern-field

**URL:** <https://discuss.elastic.co/t/could-not-locate-that-index-pattern-field/200147>\
**Category:** Beats\
**Tags:** filebeat\
**Created:** [September 19, 2019, 8:08am UTC](https://discuss.elastic.co/t/could-not-locate-that-index-pattern-field/200147 "2019-09-19T08:08:22Z")\
**Posts on this page:** 4\
**Page:** 1

<div class="post-metadata">

**Author:** ![Ludovic9](https://avatars.discourse-cdn.com/v4/letter/l/977dab/32.png) [@Ludovic9](https://discuss.elastic.co/u/Ludovic9)\
**Post date:** [September 19, 2019, 8:08am UTC](https://discuss.elastic.co/t/could-not-locate-that-index-pattern-field/200147/1 "2019-09-19T08:08:22Z")

</div>

Hello,  
I have some questions about this error I have when I run a visualization "Unique IPs map [Filebeat Apache2]".  
I'm using filbeat to send logs of filezilla to logstash then to elasticsearch. The index name is "filebeat", the template is filebeat too. Everything is fine since yesterday.

I have configured filebeat with apache module to send logs of a web server.  
I have put this :

```
setup.template.name: "filebeat"
setup.template.pattern: "filebeat-*"
index: "filebeat-web-%{+yyyy.MM.dd}"

```

It works fine, in filebeat, I see logs from apache and filezilla but when I run the visualization "Unique IPs map [Filebeat Apache2]", I have this error :

> Could not locate that index-pattern-field (id: apache2.access.geoip.location)

In the index pattern, I don't see this field, I have

> apache2.access.geoip.location.lat  
> apache2.access.geoip.location.lon

It seems I have to upload a new template from filebeat to put this new field in the template.  
I have to overwrite the existent ? Is it safe ? What's the impact for the already log, visualization & dashboard ?

---

<div class="post-metadata">

**Author:** ![Ludovic9](https://avatars.discourse-cdn.com/v4/letter/l/977dab/32.png) [@Ludovic9](https://discuss.elastic.co/u/Ludovic9)\
**Post date:** [September 19, 2019, 12:46pm UTC](https://discuss.elastic.co/t/could-not-locate-that-index-pattern-field/200147/2 "2019-09-19T12:46:22Z")

</div>

On a new server, I have installed filebeat and started it, now I have a lot of new fields in my index pattern " filebeat-\*".

I see the field apache2.access.geoip.location but he's in conflict with another one.

To fix it, I have to close the other index and re-index ?

thanks for your help.

---

<div class="post-metadata">

**Author:** ![Ludovic9](https://avatars.discourse-cdn.com/v4/letter/l/977dab/32.png) [@Ludovic9](https://discuss.elastic.co/u/Ludovic9)\
**Post date:** [September 20, 2019, 11:33am UTC](https://discuss.elastic.co/t/could-not-locate-that-index-pattern-field/200147/3 "2019-09-20T11:33:54Z")

</div>

the solution was to reindex and refresh the mapping !  
All cleared

---

<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:** [October 18, 2019, 11:33am UTC](https://discuss.elastic.co/t/could-not-locate-that-index-pattern-field/200147/4 "2019-10-18T11:33:58Z")

</div>

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