When it is useful to have multiple config files for a single Kibana instance?

Elastic Stack Kibana
1

When is it useful to have multiple config files for a single Kibana instance?

$ ./bin/kibana --help
    -c, --config <path>    Path to the config file, use multiple --config args to include multiple config files
2

It's a classic pattern for config files if you have different environments, but they share most of the settings.
There's a "base.kibana.yml" with the shared stuff, then a "prod.kibana.yml" filling in the prod ES clust and a "dev.kibana.yml" filling in the dev ES cluster

3

@flash1293 So Kibana joins the configs, right?

./bin/kibana -c base.kibana.yml -c prod.kibana.yml
4

Yes, that's the idea AFAIK

5

This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.