To validate some scenario, I had to delete .kibana_1 index. Now I try to access kibana UI and a kibana index named .kibana gets created. After this I am not able to create any new index pattern or view any logs on kibana.
Why this .kibana index is created instead of .kibana_1? And is there any way to handle this apart from deleting .kibana index and restaring kibana pod?
@thomasneirynck
Thanks for your response!
I understand, but in a scenario where all my data(indices) gets deleted, as an end user I will not know this and I will try to access kibana UI. In this case .kibana index will get created (instead of kibana_1) and I will not be able to do anything on kibana UI because of this.
Also, why is it that this .kibana index does not allow us to create or viasualize anything on the UI?
Apache, Apache Lucene, Apache Hadoop, Hadoop, HDFS and the yellow elephant
logo are trademarks of the
Apache Software Foundation
in the United States and/or other countries.