# Dashboards and indices lost

**URL:** <https://discuss.elastic.co/t/dashboards-and-indices-lost/93569>\
**Category:** Elasticsearch\
**Created:** [July 18, 2017, 11:44am UTC](https://discuss.elastic.co/t/dashboards-and-indices-lost/93569 "2017-07-18T11:44:10Z")\
**Posts on this page:** 5\
**Page:** 1

<div class="post-metadata">

**Author:** ![leoponton](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/leoponton/32/19354_2.png) [@leoponton](https://discuss.elastic.co/u/leoponton)\
**Post date:** [July 18, 2017, 11:44am UTC](https://discuss.elastic.co/t/dashboards-and-indices-lost/93569/1 "2017-07-18T11:44:10Z")

</div>

Periodically Kibana or Logstash loses its memory.

Even though I have created and saved dashboards I receive the following message:

> Looks like you don’t have any dashboards. Let’s create some!

Similarly with indices and visualizations - none are found.

The data is still intact and once the index is recreated, everything works fine.

I previously installed and removed X-Pack. Is it possible that there is still something that needs cleaning up?

[http://127.0.0.1:9200/\_cat/indices/](http://127.0.0.1:9200/_cat/indices/) reveals the following (snipped):

```
yellow open wifi-firewalls-2017.07.15 8ROe6dENQsii4CLTgDPTiQ 5 1 12674 0 3.6mb 3.6mb
yellow open wg-firewalls-2017.07.16 fjZ7lIuHS-aMFAYjT_e0-w 5 1 2373882 0 2.2gb 2.2gb
yellow open pfs-firewalls-2017.07.12 8BmTEQgpR46OcOIvHPppEA 5 1 331975 0 169.2mb 169.2mb
yellow open pfs-firewalls-2017.07.17 lvgLze4FStqo-Lsf-iqabA 5 1 348754 0 181.9mb 181.9mb
yellow open ukf-firewalls-2017.07.15 vcbD2_ZwTHyj2g2yJ2Ikug 5 1 87979 0 76.3mb 76.3mb
yellow open .kibana AkYiT9abQBCGR51iRC3WPQ 1 1 5 0 43.8kb 43.8kb
yellow open wifi-firewalls-2017.07.17 W-G5rfjeRk2vMEDigx-Jcw 5 1 19737 0 6mb 6mb
yellow open wg-firewalls-2017.07.18 VP434q-7QVuEGPSkcb-54g 5 1 2707463 0 2.8gb 2.8gb

```

---

<div class="post-metadata">

**Author:** ![geekpete](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/geekpete/32/20409_2.png) [@geekpete](https://discuss.elastic.co/u/geekpete)\
**Post date:** [July 21, 2017, 6:30am UTC](https://discuss.elastic.co/t/dashboards-and-indices-lost/93569/2 "2017-07-21T06:30:14Z")

</div>

If the .kibana index (where visualisation config is stored) was deleted or removed due to issues with the data path, then this is one scenario that would reset your visualisations.

---

<div class="post-metadata">

**Author:** ![leoponton](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/leoponton/32/19354_2.png) [@leoponton](https://discuss.elastic.co/u/leoponton)\
**Post date:** [July 25, 2017, 8:54am UTC](https://discuss.elastic.co/t/dashboards-and-indices-lost/93569/3 "2017-07-25T08:54:12Z")

</div>

Thanks.  
Bit silly really - I had a cron job deleting indices older than 7 days. It never occurred to me that it would also be deleting the .kibana index.

I have now included the kibana filter in the curator config.

---

<div class="post-metadata">

**Author:** ![geekpete](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/geekpete/32/20409_2.png) [@geekpete](https://discuss.elastic.co/u/geekpete)\
**Post date:** [July 25, 2017, 9:16am UTC](https://discuss.elastic.co/t/dashboards-and-indices-lost/93569/4 "2017-07-25T09:16:38Z")

</div>

Glad to see you’ve solved it. 🙂

—  
Regards,

Peter Dyson

---

<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:** [August 22, 2017, 9:16am UTC](https://discuss.elastic.co/t/dashboards-and-indices-lost/93569/5 "2017-08-22T09:16:47Z")

</div>

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