[Nagios-devel] Proposal to extend "Implied Inheritance"
Posted: Fri Nov 13, 2009 9:08 am
Hi List,
I think the -Implied Inheritance- functionality is something which is ver=
y useful. Especially to services.
Currently only these service variables are inherited from the host config=
uration:
contact_groups
notification_interval
notification_period
Wouldn't it be interesting to extend this functionality to inherit all ot=
her host parameters a service has in common with a host definition?=20
(except name, action url there might be on or two more obvious ones)
Especially: max_check_attempts, normal_check_interval, retry_check_interv=
al
In our case we would benefit from this because:
Our servers are acccording to a company definition split into core, produ=
ction, development, test
If services could inherit the common parameters from the host definition,=
we would only need 1 service template which could serve all.
This is of course a case which applies to my specific situation, but it c=
ould be beneficial in a multitude of other cases.
Dev's what are your thoughts?
--=20
Jelle Smet
http://www.smetj.net
This post was automatically imported from historical nagios-devel mailing list archives
Original poster: [email protected]
I think the -Implied Inheritance- functionality is something which is ver=
y useful. Especially to services.
Currently only these service variables are inherited from the host config=
uration:
contact_groups
notification_interval
notification_period
Wouldn't it be interesting to extend this functionality to inherit all ot=
her host parameters a service has in common with a host definition?=20
(except name, action url there might be on or two more obvious ones)
Especially: max_check_attempts, normal_check_interval, retry_check_interv=
al
In our case we would benefit from this because:
Our servers are acccording to a company definition split into core, produ=
ction, development, test
If services could inherit the common parameters from the host definition,=
we would only need 1 service template which could serve all.
This is of course a case which applies to my specific situation, but it c=
ould be beneficial in a multitude of other cases.
Dev's what are your thoughts?
--=20
Jelle Smet
http://www.smetj.net
This post was automatically imported from historical nagios-devel mailing list archives
Original poster: [email protected]