I'm having sort of a problem with a double kibana installation on top of a single Elastic cluster (currently using 6.7 stack, basic license).
The second kibana has this setting: kibana.index: ".my-second-app-kibana" and works just fine alongside with the main kibana instance.
I have an elastic (3rd party) plugin to allow access only to a subset of indices (my-second-app*) and .my-second-app-kibana*.
The problem arises when the second kibana tries to create ancillary indices like .kibana_task_manager, failing.
Would it be possible to use the same setting specified for the kibana.index parameter as a prefix for all the other indices kibana need to create (eg: .my-second-app-kibana_task_manager)?
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.