Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable
On Tue, May 17, 2011 at 2:27 PM, Andreas Ericsson wrote:
> Ahoy (again).
> [... service sets]
>
Hi,
Why not use a "service template on host template" feature instead? The idea
is near the second one you proposed. If you add an host_name to a service
that is a template, it will generate such service for all hosts that will
use this template. So when all your services are defined and lined in the
good host templates you will defined :
define host {
use Linux, Oracle, WhatEver
}
And the Linux, Oracle, WhatEver are regular host templates, with some
services templates linked for each of them. It's more natural for users to
think about "templates" than to use a new property. So for example the Linu=
x
template will add linux admins as contacts and will add all Linux standard
services checks (/, /var, memory, swap,...).
We already got all elements we need (template on template is not allowed, s=
o
there is no risk in breaking existing configuration), it will be easier for
configuration tools than a new object. It will be just like your solution
N=B02 a little more hard to exchange such "sets" (but in the sample
configuration we can just put a configuration file by sets for example).
It's what we add in Shinken, and it work quite well
Jean
>
> --
> Andreas Ericsson [email protected]
> OP5 AB www.op5.se
> Tel: +46 8-230225 Fax: +46 8-230231
>
>
--00235446fce4b1a3dd04a3781738
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable
On Tue, May 17, 2011 at 2:27 PM, Andreas=
Ericsson <[email protected]&=
gt; wrote:
Ahoy (again).
[... service sets]Hi,Why not use a "=
service template on host template" feature instead? The idea is near t=
he second one you proposed. If you add an host_name to a service that is a =
template, it will generate such service for all hosts that will use this te=
mplate. So when all your services are defined and lined in the good host te=
mplates you will defined :
define host {=A0=A0 use Linux, Oracle, WhatEver}And the=
Linux, Oracle, WhatEver are regular host templates, with some services tem=
plates linked for each of them. It's more natural for users to think ab=
out "templates" than to use a new property. So for example the Li=
nux template will add linux admins as contacts and will add all Linux stand=
ard services checks (/, /var, memory, swap,...).
We already got all elements we need (template on template is not allowe=
d, so there is no risk in breaking existing configuration), it will be easi=
er for configuration tools than a new object. It will be just like your sol=
ution N=B02 a little more hard to exchange such "sets" (but in th=
e sample configuration we can just put a configuration file by sets for exa=
mple).
It's what we add in Shinken, and it work quite well :)J=
ean=A0
--
Andreas Ericsson =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 [email protected]
OP5 AB =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 www.op5.se
Tel: +46 8-230225=
=A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0Fax: +46 8-230231
--00235446fce4b1a3dd04a3781738--
This post was automatically imported from historical nagios-devel mailing list archives
Original poster: [email protected]