You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I think it would be useful to have the ability to manage multiple independent kibana instances, like the elasticsearch module does. We have different es clusters and we would like to have separate kibana instances which access these instances.
The text was updated successfully, but these errors were encountered:
Thanks for the report @hameno. You're right that this is natively supported in the Elasticsearch module, but historically there have been problems with manually creating service files since they're defined separately from the upstream packages. I've opened up an Elasticsearch issue to discuss the possibility of shipping templated systemd units with Elasticsearch and will open a similar discussion with Kibana if this sounds like a reasonable option for the projects, since instantiating services based on templated systemd service units would be the best way to do this going forward.
Just as a data point, what distro and version (both OS and kibana) would you be running multiple instances on?
See the comment here and over in voxpupuli/puppet-elasticsearch#1025 . If multiple instance support is a pretty crucial feature for some people, we can potentially add some helper documentation for the repo regarding how to achieve this with Docker - let me know if that's the case, and we can add to the README if so. 👍
Feature Request
Feature Description
I think it would be useful to have the ability to manage multiple independent kibana instances, like the elasticsearch module does. We have different es clusters and we would like to have separate kibana instances which access these instances.
The text was updated successfully, but these errors were encountered: