Two contacts using the same HTTP auth?

[Marc Powell]

The question isn't quite clear but in a nutshell I interpret it to be
the following --

'I have a host that doesn't send notifications that two contacts, who
happen to be the same person, need to see."

> -----Original Message-----
> From: nagios-users-admin at lists.sourceforge.net [mailto:nagios-users-
> admin at lists.sourceforge.net] On Behalf Of C. Bensend
> Sent: Monday, August 22, 2005 1:45 PM
> To: nagios-users at lists.sourceforge.net
> Subject: [Nagios-users] Two contacts using the same HTTP auth?
> 
> 
> Hey folks,
> 
>    I've been mulling this over in my head, but I can't quite
> figure out how to do this, so I thought I'd ask here.
> 
>    I need to set up a "host" that is always down, with notifications
> disabled by default.  I have done that, no big deal.
> 
>    The problem I have, is that this fake host needs to have a
> separate contact, and I'd like to have the user use the same
> HTTP auth username and password she already has.
> 
>    Hence, she can log in using her original username and password
> just fine, but since that username is not a contact for this new
> fake host, she cannot see it (and more importantly, she cannot
> enable/disable notifications).

The question isn't quite clear, at least to me, but it would seem to me
that you just need to add the username she's logging in with as a
contact in the contact_group for the host in question. Why isn't it that
simple?

--
Marc



-------------------------------------------------------
SF.Net email is Sponsored by the Better Software Conference & EXPO
September 19-22, 2005 * San Francisco, CA * Development Lifecycle Practices
Agile & Plan-Driven Development * Managing Projects & Teams * Testing & QA
Security * Process Improvement & Measurement * http://www.sqe.com/bsce5sf
_______________________________________________
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