# Logstash pass through Index Templates

**URL:** <https://discuss.elastic.co/t/logstash-pass-through-index-templates/287487>\
**Category:** Logstash\
**Created:** [October 23, 2021, 12:21pm UTC](https://discuss.elastic.co/t/logstash-pass-through-index-templates/287487 "2021-10-23T12:21:08Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![gose](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/gose/32/37875_2.png) [@gose](https://discuss.elastic.co/u/gose)\
**Post date:** [October 23, 2021, 12:21pm UTC](https://discuss.elastic.co/t/logstash-pass-through-index-templates/287487/1 "2021-10-23T12:21:08Z")

</div>

I send all my data through Logstash. Each time there's a new Elastic release, I have to export the Index Templates for each Beat I'm using (Filebeat, Metricbeat, Heartbeat, & APM Server) and then hand-load them into Elasticsearch via Dev Tools. If I forget to do this and upgrade a host running one of the Beats, it will start sending data to a new index and create its own Mapping because the index templates won't match on the version (e.g., apm-7.15.1-2021.10.23). This causes the UIs in Kibana to stop working. I then have to load the newest Index Templates for that Beat and go back and delete any indices that have already been created matching that version, so they get re-created with the right Mapping, before the UI's light up again.

Is there an easier way?

---

<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:** [November 20, 2021, 12:21pm UTC](https://discuss.elastic.co/t/logstash-pass-through-index-templates/287487/2 "2021-11-20T12:21:21Z")

</div>

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