Re: [Nagios-devel] Proposal to extend "Implied Inheritance"
Posted: Fri Nov 13, 2009 5:28 pm
--000325574fb2984fa6047843fc1c
Content-Type: text/plain; charset=ISO-8859-1
It might be worse having functionality to define which parameters should be
inherited. But I don't think we should automatically do it for all - I
really like nagios to warn me that these were not properly defined in
majority of cases. The check parameters you listed though is ok for the use
case you provided.
Perhaps the way to do it is define one parameter in host definition that
says that parameters there can be inherited by services. This parameter by
itself would not be inheritable (i.e. when you define another host that
"uses" it) so it allows you to set the list of inheritable parameters as a
special template.
On Fri, Nov 13, 2009 at 1:07 AM, Jelle Smet wrote:
> Hi List,
>
> I think the -Implied Inheritance- functionality is something which is very
> useful. Especially to services.
>
> Currently only these service variables are inherited from the host
> configuration:
> contact_groups
> notification_interval
> notification_period
>
> Wouldn't it be interesting to extend this functionality to inherit all
> other host parameters a service has in common with a host definition?
> (except name, action url there might be on or two more obvious ones)
>
> Especially: max_check_attempts, normal_check_interval, retry_check_interval
>
> In our case we would benefit from this because:
> Our servers are acccording to a company definition split into core,
> production, 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
> could be beneficial in a multitude of other cases.
>
> Dev's what are your thoughts?
>
>
> --
> Jelle Smet
> http://www.smetj.net
>
>
> ------------------------------------------------------------------------------
> Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day
> trial. Simplify your report design, integration and deployment - and focus
> on
> what you do best, core application coding. Discover what's new with
> Crystal Reports now. http://p.sf.net/sfu/bobj-july
> _______________________________________________
> Nagios-devel mailing list
> [email protected]
> https://lists.sourceforge.net/lists/lis ... gios-devel
>
--000325574fb2984fa6047843fc1c
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable
It might be worse having functionality to define which parameters shoul=
d be inherited. But I don't think we should automatically do it for all=
- I really like nagios to warn me that these were not properly defined in =
majority of cases. The check parameters you listed though is ok for the use=
case you provided.
Perhaps the way to do it is define one parameter in host definition tha=
t says that parameters there can be inherited by services. This parameter b=
y itself would not be inheritable (i.e. when you define another host that &=
quot;uses" it) so it allows you to set the list of inheritable paramet=
ers as a special template.
On Fri, Nov 13, 2009 at 1:07 AM, Jelle Smet =
<[email protected]> wrote:
Hi List,
I think the -Implied Inheritance- functionality is something which is very =
useful. Especially to services.
Currently only these service variables are inherited from the host configur=
ation:
=A0 =A0 =A0 =A0contact_groups
=A0 =A0 =A0 =A0notification_interval
=A0 =A0 =A0 =A0notification_period
Wouldn't it be interesting to extend this functionality to inherit all =
other host parameters a service has in common with a host definition?
(except name, action url there might be on or two more obvious ones)
E
...[email truncated]...
This post was automatically imported from historical nagios-devel mailing list archives
Original poster: [email protected]
Content-Type: text/plain; charset=ISO-8859-1
It might be worse having functionality to define which parameters should be
inherited. But I don't think we should automatically do it for all - I
really like nagios to warn me that these were not properly defined in
majority of cases. The check parameters you listed though is ok for the use
case you provided.
Perhaps the way to do it is define one parameter in host definition that
says that parameters there can be inherited by services. This parameter by
itself would not be inheritable (i.e. when you define another host that
"uses" it) so it allows you to set the list of inheritable parameters as a
special template.
On Fri, Nov 13, 2009 at 1:07 AM, Jelle Smet wrote:
> Hi List,
>
> I think the -Implied Inheritance- functionality is something which is very
> useful. Especially to services.
>
> Currently only these service variables are inherited from the host
> configuration:
> contact_groups
> notification_interval
> notification_period
>
> Wouldn't it be interesting to extend this functionality to inherit all
> other host parameters a service has in common with a host definition?
> (except name, action url there might be on or two more obvious ones)
>
> Especially: max_check_attempts, normal_check_interval, retry_check_interval
>
> In our case we would benefit from this because:
> Our servers are acccording to a company definition split into core,
> production, 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
> could be beneficial in a multitude of other cases.
>
> Dev's what are your thoughts?
>
>
> --
> Jelle Smet
> http://www.smetj.net
>
>
> ------------------------------------------------------------------------------
> Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day
> trial. Simplify your report design, integration and deployment - and focus
> on
> what you do best, core application coding. Discover what's new with
> Crystal Reports now. http://p.sf.net/sfu/bobj-july
> _______________________________________________
> Nagios-devel mailing list
> [email protected]
> https://lists.sourceforge.net/lists/lis ... gios-devel
>
--000325574fb2984fa6047843fc1c
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable
It might be worse having functionality to define which parameters shoul=
d be inherited. But I don't think we should automatically do it for all=
- I really like nagios to warn me that these were not properly defined in =
majority of cases. The check parameters you listed though is ok for the use=
case you provided.
Perhaps the way to do it is define one parameter in host definition tha=
t says that parameters there can be inherited by services. This parameter b=
y itself would not be inheritable (i.e. when you define another host that &=
quot;uses" it) so it allows you to set the list of inheritable paramet=
ers as a special template.
On Fri, Nov 13, 2009 at 1:07 AM, Jelle Smet =
<[email protected]> wrote:
Hi List,
I think the -Implied Inheritance- functionality is something which is very =
useful. Especially to services.
Currently only these service variables are inherited from the host configur=
ation:
=A0 =A0 =A0 =A0contact_groups
=A0 =A0 =A0 =A0notification_interval
=A0 =A0 =A0 =A0notification_period
Wouldn't it be interesting to extend this functionality to inherit all =
other host parameters a service has in common with a host definition?
(except name, action url there might be on or two more obvious ones)
E
...[email truncated]...
This post was automatically imported from historical nagios-devel mailing list archives
Original poster: [email protected]