# Filebeat 7.3.1 - Exiting: setup.template.name and setup.template.pattern have to be set if index name is modified

**URL:** <https://discuss.elastic.co/t/filebeat-7-3-1-exiting-setup-template-name-and-setup-template-pattern-have-to-be-set-if-index-name-is-modified/266204>\
**Category:** Beats\
**Created:** [March 4, 2021, 9:43am UTC](https://discuss.elastic.co/t/filebeat-7-3-1-exiting-setup-template-name-and-setup-template-pattern-have-to-be-set-if-index-name-is-modified/266204 "2021-03-04T09:43:44Z")\
**Posts on this page:** 4\
**Page:** 1

<div class="post-metadata">

**Author:** ![dcenaculo](https://avatars.discourse-cdn.com/v4/letter/d/f14d63/32.png) [@dcenaculo](https://discuss.elastic.co/u/dcenaculo)\
**Post date:** [March 4, 2021, 9:43am UTC](https://discuss.elastic.co/t/filebeat-7-3-1-exiting-setup-template-name-and-setup-template-pattern-have-to-be-set-if-index-name-is-modified/266204/1 "2021-03-04T09:43:45Z")

</div>

Hi,

I'm using **Elastic Stack 7.3.1** and **Filebeat 7.3.1**. Now, when I try to start the filebeat, the following message appears:

```
PS C:\filebeat-7.3.1-windows-x86_64> .\filebeat.exe
Exiting: setup.template.name and setup.template.pattern have to be set if index name is modified

```

It was working fine through the logstash but I must have done something bad in the meantime ...

When I try to use some Filebeat Kibana's Dashboard, it gives the following message:

```
Could not locate that index-pattern (id: filebeat-*), click here to re-create it

```

I have already tried to recreate the index-pattern in Kibana but it continues to give the same error. Anyway, at this point, the filebeat doesn't even start.

Where do I start in order to reset Filebeat and its index-patterns to the default configuration (ELK 7.3.1)?

I appreciate all the help because I have little experience and I need to collect logs from an FTPS server and try to present some graphs of its use ...

Thanks in Advance,  
Daniel

---

<div class="post-metadata">

**Author:** ![dcenaculo](https://avatars.discourse-cdn.com/v4/letter/d/f14d63/32.png) [@dcenaculo](https://discuss.elastic.co/u/dcenaculo)\
**Post date:** [March 4, 2021, 10:40am UTC](https://discuss.elastic.co/t/filebeat-7-3-1-exiting-setup-template-name-and-setup-template-pattern-have-to-be-set-if-index-name-is-modified/266204/2 "2021-03-04T10:40:30Z")

</div>

If I use Logstash I can start Filebeat and it create daily indices:

> filebeat-2021.03.03  
> filebeat-2021.03.04

But when I try to use Filebeat **visualizations** it gives an error:

> There is a problem with this saved object
> 
> The index pattern associated with this object no longer exists.
> 
> If you know what this error means, go ahead and fix it — otherwise click the delete button above.

Or try to use filebeat dashboards, it also gives an error:

> Could not locate that index-pattern (id: filebeat-\*), [click here to re-create it](http://10.146.114.66:5601/app/kibana#/management/kibana/index_pattern)

How can I rebuild this index-pattern well?

Thanks in Advance,  
Daniel

---

<div class="post-metadata">

**Author:** ![mtojek](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/mtojek/32/63863_2.png) [@mtojek](https://discuss.elastic.co/u/mtojek)\
**Post date:** [March 5, 2021, 9:52am UTC](https://discuss.elastic.co/t/filebeat-7-3-1-exiting-setup-template-name-and-setup-template-pattern-have-to-be-set-if-index-name-is-modified/266204/3 "2021-03-05T09:52:50Z")

</div>

I'm wondering if it's not a similar thread: [Filebeat Index Issue - template pattern / name](https://discuss.elastic.co/t/filebeat-index-issue-template-pattern-name/133738)

---

<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:** [April 2, 2021, 9:53am UTC](https://discuss.elastic.co/t/filebeat-7-3-1-exiting-setup-template-name-and-setup-template-pattern-have-to-be-set-if-index-name-is-modified/266204/4 "2021-04-02T09:53:36Z")

</div>

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