2 Bugs - no "run check" button and no args with template

[eloyd]

Two issues, likely related, that I consider bugs. So do our customers.

This behavior is identified on Nagios XI 5.3.3 and 5.3.4 but we have not yet tested on 5.4.0:

We have a service (DNS check) that includes an XI Wizard template (xiwizard_website_dns_service). The service has the check command blank and arg1 blank.

The first issue is that there is no "run check command" blue button to test the service check unless the check command has something in it. Since this is being provided by the template, this should still be valid.

The second issue is that if we add something to arg1 in the service, but still leave check command blank, then the argument is not actually added to the service check. This can be confirmed by a diff of the before and after versions of objects.cache.

If we add the check_xi_service_dns command to check_command on the service (this is the check command from the template) then both the blue "run check command" appears and the argument gets processed correctly.

We believe both of these things to be bugs. The run check button should be available so long as the template expansion creates a valid configuration, and you should be able to specify/override arguments at the service level without having to specify the check command if it's being placed in the template.

[BanditBBS]

Eric, for the second part, that is expected behavior from past conversations on the forums. I actually asked it before. If the service inherits the command from template then it also inherits ARGS and locally defined ones do not override. I think its be nice if they could though, for sure, but that'd require a feature request for Nagios Core I believe.

[eloyd]

Then consider it a feature request. It only makes sense that if X is specified at level 1 (the template) and Y is specified at level 2 (the service) Y takes precedence over X, even if X is blank.

[BanditBBS]

Then consider it a feature request. It only makes sense that if X is specified at level 1 (the template) and Y is specified at level 2 (the service) Y takes precedence over X, even if X is blank.

Oh, I agree it makes sense, just requires a bit of reworking how Nagios Core works. Put in the feature request for Core and I'll instantly +1 it

[eloyd]

https://github.com/NagiosEnterprises/na ... issues/317

[lmiltchev]

For issue #1 - I don't think it is a bug report. The "Run Check Command" hasn't been intended to work this way. Having said that, I believe it *should* show up (and work) when commands are inherited from templates. I filed an internal feature request (TASK ID 10817). Thanks!