The Director aims to be your new favourite Icinga config deployment tool. Director is designed for those who want to automate their configuration deployment and those who want to grant their “point & click” users easy access to the configuration.
We are using arrays to define lists which are used in checks. e.g. check_disk for the param "-I", "--ignore-eregi-path". So we define in the template a base list of folder/mountpoints, which the check command shouldn't check for all servers.
But sometimes a server need some special folders to except. So we define this at the host/service object. And here it gets tricky and confusing. Because the director overwrites the values of the array from the template with the values from the host/service object, This is usually correct as far as it goes. BUT, if you enter new values, it looks like that the values from the templates gets inherited, what you can see here:
.
Anyway if you don't enter own values in the arrays in the host/service object, it looks like this
And because of the way of overwriting array values in the templates with array values from the host/service object, you have also to re-enter them in the host/service object, if they are also needed, which usally are.
So for us there are three options:
-> Merge the array values from the template and the specific values in the host/service object
-> Offer an option to "import" the values from the template into the host/service object.
-> don't show in the import field of an array the values from the template, so nobody gets confuesd
Your Environment
Director version (System - About): 1.10.2
Icinga Web 2 version and modules (System - About): 2.11.4
carraroj
commented
1 year ago
We are using arrays to define lists which are used in checks. e.g. check_disk for the param "-I", "--ignore-eregi-path". So we define in the template a base list of folder/mountpoints, which the check command shouldn't check for all servers.
But sometimes a server need some special folders to except. So we define this at the host/service object. And here it gets tricky and confusing. Because the director overwrites the values of the array from the template with the values from the host/service object, This is usually correct as far as it goes. BUT, if you enter new values, it looks like that the values from the templates gets inherited, what you can see here:
.
Anyway if you don't enter own values in the arrays in the host/service object, it looks like this
And because of the way of overwriting array values in the templates with array values from the host/service object, you have also to re-enter them in the host/service object, if they are also needed, which usally are.
So for us there are three options: -> Merge the array values from the template and the specific values in the host/service object -> Offer an option to "import" the values from the template into the host/service object. -> don't show in the import field of an array the values from the template, so nobody gets confuesd
Your Environment
icinga2 --version): 2.13.6