Kibana4 does not use configured index name when Kibana3 index is present

[markbastiaans]

I'm currently running an ELK stack on a single node and was experimenting with Kibana4. While I have specified a different index name in the Kibana4 configuration, Kibana4 defaults to the existing Kibana3 index. I have not found a workaround except for deleting the Kibana3 index.

Configuration:

• CentOS 6
• Single ES node (1.4 beta 1) installed from RPM
• Kibana3 with transparent proxy (nginx) to ES
• Kibana4 from tar
• Logstash 1.4.2 installed from repository

Issue:

• Kibana4 does not use specified index name in kibana.yml and defaults to the existing Kibana3 index (kibana-int)

Workaround:

• Deleting the Kibana3 index seems neccessary for Kibana4 to work

[rashidkpc]

I'm unable to replicate this, changing the index name in kibana.yml seems to work perfectly. Perhaps a caching issue?

[markbastiaans]

I've tried again after using a workaround for Logstash (see #1629) and cannot reproduce it either. I did empty the cache before and had Logstash disabled instead of using a workaround.