Well, just spent 30 minutes trying every combination of service/template, command/no command, args/no args, and everything seems to align with what you're saying.
However, Sam has pointed out that, while the args are not written to file anywhere, they are still likely generated in-place when the check is run.
Template inheritance issue?
Re: Template inheritance issue?
Former Nagios employee
Re: Template inheritance issue?
So my question is, is this a bug or is It supposed to work this way? If a bug, I'll file a report.
2 of XI5.6.14 Prod/DR/DEV - Nagios LogServer 2 Nodes
See my projects on the Exchange at BanditBBS - Also check out my Nagios stuff on my personal page at Bandit's Home and at github
See my projects on the Exchange at BanditBBS - Also check out my Nagios stuff on my personal page at Bandit's Home and at github
Re: Template inheritance issue?
They are not and my checks are broken if I try.tmcdonald wrote:Well, just spent 30 minutes trying every combination of service/template, command/no command, args/no args, and everything seems to align with what you're saying.
However, Sam has pointed out that, while the args are not written to file anywhere, they are still likely generated in-place when the check is run.
2 of XI5.6.14 Prod/DR/DEV - Nagios LogServer 2 Nodes
See my projects on the Exchange at BanditBBS - Also check out my Nagios stuff on my personal page at Bandit's Home and at github
See my projects on the Exchange at BanditBBS - Also check out my Nagios stuff on my personal page at Bandit's Home and at github
-
slansing
- Posts: 7698
- Joined: Mon Apr 23, 2012 4:28 pm
- Location: Travelling through time and space...
Re: Template inheritance issue?
Revising my original response to your question with this:
You cannot pass arguments through a template because it will not pass them through to the command_definition with "!" separators it will pass them as plain text so with the template's $ARG3$ you were defining, it was basically dropping it on the service definition with no !'s to pass it through as a additional argument in the check command at the $ARG3$ position if that makes sense. You can only get this if you add the arguments from the service definition itself so they are already assigned by the time the template is overlaid.
So it would be a "sudo" feature? I'm not sure how this would be worked in at this time.
You cannot pass arguments through a template because it will not pass them through to the command_definition with "!" separators it will pass them as plain text so with the template's $ARG3$ you were defining, it was basically dropping it on the service definition with no !'s to pass it through as a additional argument in the check command at the $ARG3$ position if that makes sense. You can only get this if you add the arguments from the service definition itself so they are already assigned by the time the template is overlaid.
So it would be a "sudo" feature? I'm not sure how this would be worked in at this time.
Re: Template inheritance issue?
Ok, lock her up. I can work around it just fine.
2 of XI5.6.14 Prod/DR/DEV - Nagios LogServer 2 Nodes
See my projects on the Exchange at BanditBBS - Also check out my Nagios stuff on my personal page at Bandit's Home and at github
See my projects on the Exchange at BanditBBS - Also check out my Nagios stuff on my personal page at Bandit's Home and at github
Re: Template inheritance issue?
Ha! It was not me this time . . . . back to the mines . . . .
Former Nagios employee
"It is turtles. All. The. Way. Down. . . .and maybe an elephant or two."
VI VI VI - The editor of the Beast!
Come to the Dark Side.
"It is turtles. All. The. Way. Down. . . .and maybe an elephant or two."
VI VI VI - The editor of the Beast!
Come to the Dark Side.