# Need to recreate/reindex when upgrading beats?

**URL:** <https://discuss.elastic.co/t/need-to-recreate-reindex-when-upgrading-beats/255783>\
**Category:** Beats\
**Tags:** metricbeat\
**Created:** [November 18, 2020, 5:03am UTC](https://discuss.elastic.co/t/need-to-recreate-reindex-when-upgrading-beats/255783 "2020-11-18T05:03:04Z")\
**Posts on this page:** 4\
**Page:** 1

<div class="post-metadata">

**Author:** ![rgeisman](https://avatars.discourse-cdn.com/v4/letter/r/e480ec/32.png) [@rgeisman](https://discuss.elastic.co/u/rgeisman)\
**Post date:** [November 18, 2020, 5:03am UTC](https://discuss.elastic.co/t/need-to-recreate-reindex-when-upgrading-beats/255783/1 "2020-11-18T05:03:04Z")

</div>

Greetings all. I have some questions in general about when beats upgrade. We have ELK running on a cluster where an orchestration platform upgrades the beats automatically. So using Logstash of course when I first used a beat I had to stop Logstash and inject the index templates by hand.

My question is do we need to do this process each time the beat is updated? Say I upgraded to Metricbeat 7.9 and through the command line injected the index templates into ES after stopping Logstash. When the beat upgrades to 7.10 do I need to do that again? Does the index structure (mapping) change when beats upgrade?

I keep seeing with the beats that there is this 3-4 lag in Kibana between when stuff is supposedly getting ingested and when it shows up in Kibana. Wonder if this is related. Also, I notice if I delete an index pattern after a beat upgrade, and then make a new one, the new "metricbeat-\*" pattern now has mapping conflicts.

This is an EXTREMELY confusing situation. Just saying. Thanks!

---

<div class="post-metadata">

**Author:** ![warkolm](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/warkolm/32/39224_2.png) [@warkolm](https://discuss.elastic.co/u/warkolm)\
**Post date:** [November 18, 2020, 5:43am UTC](https://discuss.elastic.co/t/need-to-recreate-reindex-when-upgrading-beats/255783/2 "2020-11-18T05:43:35Z")

</div>

It'd be better to do it, so you know you are always running the latest templates.  
Otherwise you may get caught out.

---

<div class="post-metadata">

**Author:** ![dadoonet](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/dadoonet/32/137187_2.png) [@dadoonet](https://discuss.elastic.co/u/dadoonet)\
**Post date:** [November 18, 2020, 6:29am UTC](https://discuss.elastic.co/t/need-to-recreate-reindex-when-upgrading-beats/255783/3 "2020-11-18T06:29:46Z")

</div>

Adding that I think that beats are automatically upgrading the templates but only when directly connected to Elasticsearch.

It does not happen when connected through Logstash.

---

<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:** [December 16, 2020, 6:29am UTC](https://discuss.elastic.co/t/need-to-recreate-reindex-when-upgrading-beats/255783/4 "2020-12-16T06:29:47Z")

</div>

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