<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=iso-8859-1">
<META content="MSHTML 5.50.4611.1300" name=GENERATOR>
<STYLE>@page Section1 {size: 8.5in 11.0in; margin: 1.0in 1.25in 1.0in 1.25in; }
P.MsoNormal {
FONT-SIZE: 12pt; MARGIN: 0in 0in 0pt; FONT-FAMILY: "Times New Roman"
}
LI.MsoNormal {
FONT-SIZE: 12pt; MARGIN: 0in 0in 0pt; FONT-FAMILY: "Times New Roman"
}
DIV.MsoNormal {
FONT-SIZE: 12pt; MARGIN: 0in 0in 0pt; FONT-FAMILY: "Times New Roman"
}
A:link {
COLOR: blue; TEXT-DECORATION: underline
}
SPAN.MsoHyperlink {
COLOR: blue; TEXT-DECORATION: underline
}
A:visited {
COLOR: purple; TEXT-DECORATION: underline
}
SPAN.MsoHyperlinkFollowed {
COLOR: purple; TEXT-DECORATION: underline
}
SPAN.EmailStyle17 {
COLOR: windowtext; FONT-FAMILY: Arial
}
DIV.Section1 {
page: Section1
}
</STYLE>
</HEAD>
<BODY lang=EN-US vLink=purple link=blue>
<DIV><SPAN class=124023615-20012003><FONT face="Comic Sans MS" color=#000080
size=2>Using the 'parents' directive, one host will effectively become dependant
on another. Plus, the status map will reflect this
hierarchy.</FONT></SPAN></DIV>
<DIV><SPAN class=124023615-20012003><FONT face="Comic Sans MS" color=#000080
size=2></FONT></SPAN> </DIV>
<DIV><SPAN class=124023615-20012003><FONT face="Comic Sans MS" color=#000080
size=2>Creating a host dependancy won't do anything to the status map. If
one host is dependant on another, I suppose you could say that the services of
the dependent host depend on the depended-on host, but the services of the
dependent host don't depend on any services of the depended-on host, unless you
explicity define that dependency. In my case, I have multiple NRPE
services dependent on one particular NRPE service on the same host, but I could
just as easily created the definition such that they were dependent on some
arbitrary other service on some arbitrary host. (Ideally, the choice would
make sense, and not be arbitrary. ;)</FONT></SPAN></DIV>
<DIV><SPAN class=124023615-20012003><FONT face="Comic Sans MS" color=#000080
size=2></FONT></SPAN> </DIV>
<DIV><SPAN class=124023615-20012003><FONT face="Comic Sans MS" color=#000080
size=2>If you can honestly say to yourself something like, "If I define
dependencies such that hosts B, C, D and E are all dependent on A, and I really
don't care what the status of hosts B, C, D and E are if the ping RTA time of
host A goes through the roof", then you may be a good candidate to define this
depedency. BUT, if host A is acting up or in a scheduled outage or
similar, and any one of host B/C/D/E suffers the pingtime problem (e.g., host
died a horrible death), then you won't get a notification. Sorry, you
created the definition, so that's how it is.</FONT></SPAN></DIV>
<DIV><SPAN class=124023615-20012003><FONT face="Comic Sans MS" color=#000080
size=2></FONT></SPAN> </DIV>
<DIV><SPAN class=124023615-20012003><FONT face="Comic Sans MS" color=#000080
size=2>If this isn't acceptable, then I'm not sure what to say. You can
put in the request for consolidating notifications, but I see some problems
right away:</FONT></SPAN></DIV>
<DIV><SPAN class=124023615-20012003><FONT face="Comic Sans MS" color=#000080
size=2></FONT></SPAN> </DIV>
<DIV><SPAN class=124023615-20012003><FONT face="Comic Sans MS" color=#000080
size=2>How would you define the consolidation logic? Wait for a predefined
threshold of hosts to squawk before sending the single notification? Wait
for a quorum of hosts to complain? Wait for a percentage failure?
What if that threshold isn't reached? Do you want it to wait a fixed
amount of time before sending out the consolidated message? Do you want it
to wait for a timeout of sorts (e.g., several hosts send notifications; wait 5
mins after the last one before sending out the consolidated
message)?</FONT></SPAN></DIV>
<DIV><SPAN class=124023615-20012003><FONT face="Comic Sans MS" color=#000080
size=2></FONT></SPAN> </DIV>
<DIV><SPAN class=124023615-20012003><FONT face="Comic Sans MS" color=#000080
size=2>I can't help but think that defining some sort of dependency might do
what you need to do. Take a look at the docs regarding host/service
dependencies. I know I ended up going over them several times in order to
get a clear picture of what it can do. I don't think I'm even using the
full capabilities; mine is a fairly simple config by comparison (in terms of
logic, anyway).</FONT></SPAN></DIV>
<DIV><SPAN class=124023615-20012003><FONT face="Comic Sans MS" color=#000080
size=2></FONT></SPAN> </DIV>
<DIV><SPAN class=124023615-20012003><FONT face="Comic Sans MS" color=#000080
size=2>Perhaps instead of having all the hosts funnel their dependencies into
one particular host, divide the dependencies so that you end up with 2 'master'
hosts. This would let you schedule downtime on one without ending up
'flying blind' on every other host. If one of these hosts complains, you
may not be in bad shape, but if both of the hosts complain, you could have a
major outage on your hands. But you'll still only receive the 2
notifications.</FONT></SPAN></DIV>
<DIV><SPAN class=124023615-20012003><FONT face="Comic Sans MS" color=#000080
size=2></FONT></SPAN> </DIV>
<DIV><SPAN class=124023615-20012003><FONT face="Comic Sans MS" color=#000080
size=2>Food for thought.</FONT></SPAN></DIV>
<DIV><SPAN class=124023615-20012003><FONT face="Comic Sans MS" color=#000080
size=2></FONT></SPAN> </DIV>
<DIV><SPAN class=124023615-20012003><FONT face="Comic Sans MS" color=#000080
size=2>jc</FONT></SPAN></DIV>
<BLOCKQUOTE dir=ltr
style="PADDING-LEFT: 5px; MARGIN-LEFT: 5px; BORDER-LEFT: #000080 2px solid; MARGIN-RIGHT: 0px">
<DIV class=OutlookMessageHeader dir=ltr align=left><FONT face=Tahoma
size=2>-----Original Message-----<BR><B>From:</B> Shayne Lebrun
[mailto:slebrun@muskoka.com]<BR><B>Sent:</B> Saturday, January 18, 2003 4:48
AM<BR><B>To:</B> Carroll, Jim P [Contractor]<BR><B>Subject:</B> RE:
[Nagios-users] aggregated status messages<BR><BR></FONT></DIV>
<DIV><SPAN class=547594310-18012003><FONT face=Arial color=#0000ff
size=2>Service dependancies....perhaps. But aren't services
automatically considered dependant if hosts are?</FONT></SPAN></DIV>
<DIV><SPAN class=547594310-18012003><FONT face=Arial color=#0000ff
size=2></FONT></SPAN> </DIV>
<DIV><SPAN class=547594310-18012003><FONT face=Arial color=#0000ff size=2>I
kind of like the idea of squelching 'unreachable' messages and being done with
it, but....</FONT></SPAN></DIV>
<BLOCKQUOTE dir=ltr style="MARGIN-RIGHT: 0px">
<DIV class=OutlookMessageHeader dir=ltr align=left><FONT face=Tahoma
size=2>-----Original Message-----<BR><B>From:</B> Carroll, Jim P
[Contractor] [mailto:jcarro10@sprintspectrum.com]<BR><B>Sent:</B> Friday,
January 17, 2003 6:47 PM<BR><B>To:</B> 'Shayne Lebrun';
nagios-users@lists.sourceforge.net<BR><B>Subject:</B> RE: [Nagios-users]
aggregated status messages<BR><BR></FONT></DIV>
<DIV><SPAN class=797594623-17012003><FONT face="Comic Sans MS" color=#000080
size=2>Perhaps host or service dependencies would be more to your
liking.</FONT></SPAN></DIV>
<DIV><SPAN class=797594623-17012003><FONT face="Comic Sans MS" color=#000080
size=2></FONT></SPAN> </DIV>
<DIV><SPAN class=797594623-17012003><FONT face="Comic Sans MS" color=#000080
size=2>jc</FONT></SPAN></DIV>
<BLOCKQUOTE dir=ltr
style="PADDING-LEFT: 5px; MARGIN-LEFT: 5px; BORDER-LEFT: #000080 2px solid; MARGIN-RIGHT: 0px">
<DIV class=OutlookMessageHeader dir=ltr align=left><FONT face=Tahoma
size=2>-----Original Message-----<BR><B>From:</B> Shayne Lebrun
[mailto:slebrun@muskoka.com]<BR><B>Sent:</B> Friday, January 17, 2003 3:28
PM<BR><B>To:</B> Carroll, Jim P [Contractor];
nagios-users@lists.sourceforge.net<BR><B>Subject:</B> RE: [Nagios-users]
aggregated status messages<BR><BR></FONT></DIV>
<DIV><SPAN class=853482521-17012003><FONT face=Arial color=#0000ff
size=2>Look at it this way. One of my wireless subnets just went to
hell; tripped 'service critical' messages for five or six servers, as the
ping RTA time suddenly shot up. So I got five emails. I'd
rather have gotten one email with five entries.</FONT></SPAN></DIV>
<BLOCKQUOTE dir=ltr style="MARGIN-RIGHT: 0px">
<DIV class=OutlookMessageHeader dir=ltr align=left><FONT face=Tahoma
size=2>-----Original Message-----<BR><B>From:</B>
nagios-users-admin@lists.sourceforge.net
[mailto:nagios-users-admin@lists.sourceforge.net]<B>On Behalf Of
</B>Carroll, Jim P [Contractor]<BR><B>Sent:</B> Friday, January 17, 2003
2:48 PM<BR><B>To:</B> 'Shayne Lebrun';
nagios-users@lists.sourceforge.net<BR><B>Subject:</B> RE: [Nagios-users]
aggregated status messages<BR><BR></FONT></DIV>
<DIV><SPAN class=203154619-17012003><FONT face="Comic Sans MS"
color=#000080 size=2>Read up on the 'parents' directive. Sounds
like this will do exactly what you're looking for. (This was one
of the main reasons we switched from BB to Nagios.)</FONT></SPAN></DIV>
<DIV><SPAN class=203154619-17012003><FONT face="Comic Sans MS"
color=#000080 size=2></FONT></SPAN> </DIV>
<DIV><SPAN class=203154619-17012003><FONT face="Comic Sans MS"
color=#000080 size=2><A
href="http://nagios.webdev.sprintspectrum.com/nagios/docs/xodtemplate.html#host">http://nagios.webdev.sprintspectrum.com/nagios/docs/xodtemplate.html#host</A></FONT></SPAN></DIV>
<DIV><SPAN class=203154619-17012003><FONT face="Comic Sans MS"
color=#000080 size=2></FONT></SPAN> </DIV>
<DIV><SPAN class=203154619-17012003><FONT face="Comic Sans MS"
color=#000080 size=2>jc</FONT></SPAN></DIV>
<BLOCKQUOTE dir=ltr
style="PADDING-LEFT: 5px; MARGIN-LEFT: 5px; BORDER-LEFT: #000080 2px solid; MARGIN-RIGHT: 0px">
<DIV class=OutlookMessageHeader dir=ltr align=left><FONT face=Tahoma
size=2>-----Original Message-----<BR><B>From:</B> Shayne Lebrun
[mailto:slebrun@muskoka.com]<BR><B>Sent:</B> Friday, January 17, 2003
11:33 AM<BR><B>To:</B>
nagios-users@lists.sourceforge.net<BR><B>Subject:</B> [Nagios-users]
aggregated status messages<BR><BR></FONT></DIV>
<DIV><FONT face=Arial color=#0000ff size=2><SPAN
style="FONT-SIZE: 12pt"><SPAN class=469532917-17012003>One thing I'd
love to see from Nagios would be the ability to have aggregated status
messages; I'd like to be able to tell it that when it feels the need
to send a status message, it should tell me what (if anything) is
already (still) down, what (if anything) has just come back up, and
what (if anything) has just gone down.</SPAN></SPAN></FONT></DIV>
<DIV><FONT face=Arial color=#0000ff size=2><SPAN
style="FONT-SIZE: 12pt"><SPAN
class=469532917-17012003></SPAN></SPAN></FONT> </DIV>
<DIV><FONT face=Arial color=#0000ff size=2><SPAN
style="FONT-SIZE: 12pt"><SPAN class=469532917-17012003>That way, if a
satellite router goes down, I get one email saying 'routerX down,
hosts a,b,c,d,e,f,g now unreachable' instead of getting eight or nine
emails. Also, if a subnet goes down, but things are coming
back up one by one, I can tell which is still down and which is still
up.</SPAN></SPAN></FONT></DIV>
<DIV><FONT face=Arial color=#0000ff size=2><SPAN
style="FONT-SIZE: 12pt"><SPAN
class=469532917-17012003></SPAN></SPAN></FONT> </DIV>
<DIV><FONT face=Arial color=#0000ff size=2><SPAN
style="FONT-SIZE: 12pt"><SPAN class=469532917-17012003>Makes it more
efficient for mobile devices reciving said emails,
too.</SPAN></SPAN></FONT></DIV>
<DIV><FONT face=Arial color=#0000ff size=2><SPAN
style="FONT-SIZE: 12pt"><SPAN
class=469532917-17012003></SPAN></SPAN></FONT> </DIV>
<DIV><FONT face=Arial color=#0000ff size=2><SPAN
style="FONT-SIZE: 12pt"><SPAN class=469532917-17012003>
<P><FONT size=2>Muskoka.com<BR>115 Manitoba Street<BR>Bracebridge,
Ontario<BR>P1L 2B6<BR>(705)645-6097<BR><BR>Muskoka.com is pleased to
announce<BR>New High Speed Services<BR>please visit<BR><A
target=_blank
href="http://www.muskoka.com/services.htm">http://www.muskoka.com/services.htm</A><BR>for
more
information<BR></FONT></P></SPAN></SPAN></FONT></DIV></BLOCKQUOTE></BLOCKQUOTE></BLOCKQUOTE></BLOCKQUOTE></BLOCKQUOTE></BODY></HTML>