# No indices match pattern "filebeat-\*" **URL:** \ **Category:** Elasticsearch\ **Created:** [August 3, 2018, 3:24pm UTC](https://discuss.elastic.co/t/no-indices-match-pattern-filebeat/142938 "2018-08-03T15:24:20Z")\ **Posts on this page:** 3\ **Page:** 2
**Author:** ![A\_B](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/a_b/32/17104_2.png) [@A\_B](https://discuss.elastic.co/u/A_B)\ **Post date:** [August 6, 2018, 1:52pm UTC](https://discuss.elastic.co/t/no-indices-match-pattern-filebeat/142938/21 "2018-08-06T13:52:26Z")
Well, there are _Saved searches_ and _Dashboards_ that are setup to use indices that are named `filebeat-*` (`filebeat setup -e`). That does not mean those indices are created. As I mentioned before, Filebeat will create those indices (if they don't exist) when it ships the first log message to Elasticsearch. If there are no log messages to ship, those indices will not be created. ---
**Author:** ![arrigonfr](https://avatars.discourse-cdn.com/v4/letter/a/6bbea6/32.png) [@arrigonfr](https://discuss.elastic.co/u/arrigonfr)\ **Post date:** [August 6, 2018, 1:56pm UTC](https://discuss.elastic.co/t/no-indices-match-pattern-filebeat/142938/22 "2018-08-06T13:56:49Z")
@A_B @tdasch @Charaf_Ahmed I want to thank you all for your help. A colleague was just checking the kibana dashboards and found out it was working and came to tell me. Apparently all I needed to do was restart the service after fixing the config. I was only re-running **"filebeat setup -e"** before. ---
**Author:** ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)\ **Post date:** [September 3, 2018, 1:56pm UTC](https://discuss.elastic.co/t/no-indices-match-pattern-filebeat/142938/23 "2018-09-03T13:56:52Z")
This topic was automatically closed 28 days after the last reply. New replies are no longer allowed. [Previous page](https://discuss.elastic.co/t/no-indices-match-pattern-filebeat/142938.md?page=1)