Join GitHub today
GitHub is home to over 28 million developers working together to host and review code, manage projects, and build software together.Sign up
Improve and extend template and dashboard configurations #3921
In 6.0 the template configuration changes as it is dynamically loaded. Also recently dashboards configs to load dashboards were introduced. In addition logic to load certain data on startup like pipelines were added. This issue propose a potential way forward with and extensible config format for the above cases.
The current configuration for
The template part is inside elasticsearch output as it currently only applies to the ES output.
The proposal is to place all setup related configuration options under one namespace called
This approach would have a few advantages:
The above is a breaking change and we would need to have a migration script if possible.
The above change will allow to solve some more problem in #3654. These changes are not tied to the above but it would be good to do them at the same time.
For this the config could be extended as following:
In the above the follwing changed:
referenced this issue
Apr 5, 2017
Perhaps we could reduce these to a single option (
The question here is if we want to allow overwriting any mapping setting or we explicitly add things? I'd say we start with explicit settings for the things we know are useful (number of shards, number of replicas, index numerics).
Just to have mentioned it, this will make setting up the dahsboards URL from the CLI a bit more annoying:
I also noticed that it's
I will start the migration step by step.
For the longer