Authenticated users cross-auth problem
Jamie Baddeley
jamie.baddeley at vpc.co.nz
Wed Jul 16 13:39:41 CEST 2003
Hmm. I may be confused, but you'd potentially need to construct a new
grouping for services wouldn't you? How does your proposed logic deal with a
single contact who has access to multiple services across multiple hosts? Or
do you assign a contact group to each service? Thats feels like potentially
lots of keyboard work for the typical/average nagministrator....
6 of one - half a dozen of the other really...I've not bothered either way.
It just seemed simple to tie a service dependency contruct to a contactgroup.
Or perhaps it's better to think about a customer-view group - which can be
different to a contact group....
My reality is I've got users looking at services that are actually dependent
on each other to deliver something that the PHB's understand - like WWW - You
know - expressing stuff in a "meaningful" way. DNS bone is connected to the
Firewall bone, which is connected to the Proxy/Cache bone etc etc (you get
the idea..)
I've been getting creative with service descriptions too - so this additional
level of abstraction would be handy.
Or maybe it's late and I should sleep.
maybe a thread to continue...
jamie
On Wed, 16 Jul 2003 23:00, Karl DeBisschop wrote:
> On Wed, 2003-07-16 at 05:26, Jamie Baddeley wrote:
> > Hi Greg,
> >
> > Nope you're right on the money. It seems to me that the logic is based
> > around/tied to hostgroup definitions.
> >
> > Partitioned views IMHO are a really nice aspect of Nagios. Make the
> > concept of "Online NOC" work......But it seems far more sensible to make
> > these partitions aligned to services rather than hosts - after all the
> > Nagger is service focussed not host focussed.
> >
> > Maybe if it was tied it to a service dependency definition it'd work
> > better. That'd be a really good reason to create service dependencies for
> > something other than alert-storm prevention....
> >
> > i.e customer A is dependent of service dependency thread Z & Y.
>
> In practice, won't the contact group for the service be a good indicator
> of who should be authorized to see a service?
>
> If Nagios perms were extended to allow access to members associated with
> a contact group, there would be a rationale way to express this. You
> woul need to ad login names to the contact or contact group definition.
> But for some site, that might even be all you need to do.
>
> (I haven't needed to do this, so I haven't thought alot about it -
> forgive me if this could not work for some obvious reason I'm not
> seeing)
-------------------------------------------------------
This SF.net email is sponsored by: VM Ware
With VMware you can run multiple operating systems on a single machine.
WITHOUT REBOOTING! Mix Linux / Windows / Novell virtual machines at the
same time. Free trial click here: http://www.vmware.com/wl/offer/345/0
_______________________________________________
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
More information about the Users
mailing list