Closed axelaris closed 8 years ago
Depends on the installation, I guess. Personally I'm still using Kibana3 for many things, so would prefer it stick around. Is having it around causing problems in your deployments though? If so, I guess we could drop it and those needing it can list it as a remote plugin in their deployment properties. This question was also asked in #165, so maybe I'm missing something.
Two Kibana's just brings us a bit of mess here. It's not an urgent issue, but in long term perspective I believe one of them should be removed.
Kibana 3 doesn't work with Elasticsearch 2.0 so when we merge https://github.com/logsearch/logsearch-boshrelease/pull/171 we'll remove Kibana 3
Hi guys, do we really need Kibana 3 as a ElasticSearch plugin since we have Kibana 4 there as a separate package?