------=_Part_876_32502325.1202983093114
Content-Type: multipart/alternative;
boundary="----=_Part_877_18132973.1202983093114"
------=_Part_877_18132973.1202983093114
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable
Content-Disposition: inline
Hi List,
in my last confusing topic I tried to explain a problem I've got with
configuration distribution design with nagios distributed monitoring.
I hope to clarify this topic and present a solution.
It would be nice if you can comment this again.
Actual situation with Nagios 3.x:
If I would make my life easier with configuring nagios for my distributed
system I would define some templates to control the behavior on the master
or on the slave.
f.e. on the slave a template would define a normal check_command, but no
freshness options.
on the master server the same template name would result in some other
check_command inclusive freshness options and so on.
With this possibility the service definitions on master _and_ on slave
servers would be identically but the different templates on both sides woul=
d
control "live checking" or "freshness checking".
But for this it should be possible that a template made directive should be
able to override a directive from the service definition.
I know that the default behavior is the other direction (template ->
service, but service directives are last significant).
Since Nagios 3.x allows a template addition through the "+" notation my
thoughts goes in this direction.
What would be if you were allowed to inject a special character to your
template to override a service definition (for example).
With attached patch I got exactly this behavior.
Thanks
Mark
--=20
Mark Eisenbl=E4tter
Geissendoerfer & Leschinsky GmbH
www.gl-sytemhaus.de
------=_Part_877_18132973.1202983093114
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable
Content-Disposition: inline
Hi List,in my last confusing topic I tried to explain a problem I&#=
39;ve got with configuration distribution design with nagios distributed mo=
nitoring.I hope to clarify this topic and present a solution.
It would be nice if you can comment this again.Actual situation=
with Nagios 3.x:If I would make my life easier with configuring nagios=
for my distributed system I would define some templates to control the beh=
avior on the master or on the slave.
f.e. on the slave a template would define a normal check_command, but n=
o freshness options.on the master server the same template name wou=
ld result in some other check_command inclusive freshness options and so on=
.
With this possibility the service definitions on master _and_ on slave =
servers would be identically but the different templates on both sides woul=
d control "live checking" or "freshness checking".
But for this it should be possible that a template made directive shoul=
d be able to override a directive from the service definition.I kno=
w that the default behavior is the other direction (template -> service,=
but service directives are last significant).
Since Nagios 3.x allows a template addition through the "+" n=
otation my thoughts goes in this direction.What would be if you were al=
lowed to inject a special character to your template to override a service =
definition (for example).
With attached patch I got exactly this behavior.T=
hanks Mark-- Mark Eisenbl=E4tterGeissendoerfer & Le=
schinsky GmbHwww.gl-sytemhaus.de=
------=_Part_877_18132973.1202983093114--
------=_Part_876_32502325.1202983093114
Content-Type: application/octet-stream; name=patch.diff
Content-Transfer-Encoding: base64
X-Attachment-Id: f_fcn51bok0
Content-Disposition: attachment; filename=patch.diff
LS0tIHhvZHRlbXBsYXRlLmMub3JnCTIwMDgtMDItMTQgMDk6MTE6MjcuMjU3NTY4MzQ0ICswMTAw
CisrKyB4b2R0ZW1wbGF0ZS5jCTIwMDgtMDItMTQgMDk6MjU6MjUuMDkxMTk4
...[email truncated]...
This post was automatically imported from historical nagios-devel mailing list archives
Original poster: [email protected]