Everything works! But I want more!

[Mark D. Nagel]

Andreas Ericsson wrote:

> Mark D. Nagel wrote:
>
>> You are right -- however, there is something special about hostgroups 
>> -- they list contact groups whereas hosts do not.
>
>
> This is inconsistent with how services does it. It has been fixed in 
> 2.0, which places the contact_groups variable immediately on each host 
> object instead.


I for one am definitely anxious for 2.0 to come out of alpha.  Sounds 
like it will have a lot of cool improvements.

>>  I may be wrong, but I believe if a host is not in a host group _and_ 
>> all services fail, you have to have that host in a hostgroup for 
>> notifications to be sent about the host outage.
>
>
> For version 1.x, yes, but it doesn't have anything at all to do with 
> when and how checks are being executed, so you're very much changing 
> the topic here.


Absolutely.  Since I had already admitted my original error several 
messages earlier, I was actually asking what originally lead me to my 
misunderstanding, that is, that I had observed I would not be notified 
about host down conditions unless that host was in a hostgroup. Thus, 
not so much off topic really -- if a host is not in _some_ hostgroup, 
then it can be host-checked all day long, but you won't get a host down 
notification.  Now, I'll admit that has nothing to do with the original 
poster's issue.  He wanted the GUI status to read 'OK', which it would 
despite not being in a hostgroup.  But 'very much changing the topic'?  
I don't really think so.

>>  I am not 100% on that, but investigated this after noticing the 
>> pre-flight warnings regarding hosts not being in any hostgroup.   If 
>> that is not correct, please let me know to whom a host
>> down alert is sent when the host is not in a hostgroup?  Is it the 
>> default contact in nagios.cfg?
>>
>
> There is no default contact in nagios.cfg. I suspect you mean 
> admin_email, which is shown on some of the webpages and is available 
> as a macro ($ADMINEMAIL$) for notifications and some other commands. 
> It can never be a target for notifications unless you've got a 
> seriously fishy configuration.

Yes, that is the contact I was thinking of when I wrote this personal 
message to you -- thanks for clarifying it.  I hadn't checked the docs 
at the time I wrote that, just remembered there was some default contact 
in nagios.cfg and was wondering out loud if that was perhaps the reason 
you kept claiming hostgroups were completely irrelevant.  Since you'd 
made clear that in 1.x that notifications won't be sent unless the 
problem host is in a hostgroup, I'm glad to find my original statement 
wasn't 100% off, just that I had confounded the check with the resultant 
notification.

Regards,
Mark

-- 
Mark D. Nagel, CCIE #3177 <mnagel at willingminds.com>
Principal Consultant, Willing Minds LLC
tel: 714-630-4772, fax: 714-630-4773, web: http://www.willingminds.com/



-------------------------------------------------------
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now. 
http://productguide.itmanagersjournal.com/
_______________________________________________
Nagios-users mailing list
Nagios-users at lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nagios-users
::: Please include Nagios version, plugin version (-v) and OS when reporting any issue. 
::: Messages without supporting info will risk being sent to /dev/null