Request: Ability to use ARGx fields without a command select

[Box293]

I have been playing around with how service templates and services apply inherritance.

Goal: I want to be able to use a service template but also be able to populate an ARGx field for the service (that the service template is applied to) to acheive variations of the template.

Example:
I have a command [$USER1$/check_nt -H $HOSTADDRESS$ -s "$ARG1$" -p 12489 -v -l C -w $ARG2$ -c $ARG3$]
I have a service template called "template_disk_check" and it uses the command above
This template has $ARG2$ populated with 80 and $ARG3$ populated with 90
On my hosts that I want to perform a disk check on have a service called "test server disk check" and this service has the service template "template_disk_check" applied to it.

This works great for about 95% of the hosts I am checking however there is always the exception to the rule.

Some of my hosts fall outside the warning and critical values defined in the service template. These are hosts that I am OK with having less free space and do not want to generate warnings or critical events because they fall outside the scope of the service template.

For these particular hosts I would like to be able to edit the host's service and populate the $ARG2$ and $ARG3$ fields with approporiate numbers. This would allow me to apply a variation to my service template without having to a) create another service template or b) remove the service template and apply the check directly to the service.

I have tried to make this work but if I don't select a check command in the service then any ARGx fields I populate do not get saved. When I edit the service again the fields have been lost. I have also tried selecting the check command and ONLY populating the fields I want variations on however it seems to completely ignore the service template when I do this.


I'm not saying this is an easy or quick modification I am requesting however I do feel it would extend the capabilities of templates and variations on the templates using inherritance. This should apply to hosts / host templates and services / service templates.


Please let me know if I have not clearly explained what I am requesting.

P.S. keep up the great work

[mmestnik]

I'm not sure this would be available until the underlying Nagios Core has support. I'm also unsure how this change would effect NagiosQL.

The data is stored in a single value, despite multiple GUI inputs. As you said you didn't expect it to be easy.