User x Hostgroup

[Jim Avery]

2009/4/27 Fernando - IT <faugusto.ti at gmail.com>:
>   Hi All,
>
>  Anyone knows how I can create a user for each hostgroup?
>
>  I need to create users with view right only, but each user can see
> only one hostgroup. I need do that for delegate some hostgroups.
>
> For example:
>
> Hostgroup_A can be seen only by user HAViewer.
>
> Hostgroup_B can be seen only by user HBViewer.
>
> Thanks

You can create a host template definition which specifies the
hostgroup and contact for example:

  define host {
    name HAViewer
    contact_groups  +HAViewer
    hostgroups  +HAViewer
    register 0
  }

Then in the host definition for each host in this group, put, for example:

  use  HAViewer,generic-template

or if you want a host to be a member of more than one group, that's
fine you can put:
  use  HAViewer,HBViewer,generic-template

You will of course need  the contact and contactgroup definitions and
a hostgroup definition.  The hostgroup definition can contain the bare
minimum information, for example:

  define hostgroup{
    hostgroup_name  HAViewer
    alias  HAViewer - group of hosts which can only be viewed by the
HAViewer contact group
  }

You'll need also to make sure the contacts having a limited view are
not specified in "authorized_for_all_services" or
"authorized_for_all_hosts" in your cgi.cfg file.

hth,

Jim

------------------------------------------------------------------------------
Register Now & Save for Velocity, the Web Performance & Operations 
Conference from O'Reilly Media. Velocity features a full day of 
expert-led, hands-on workshops and two days of sessions from industry 
leaders in dedicated Performance & Operations tracks. Use code vel09scf 
and Save an extra 15% before 5/3. http://p.sf.net/sfu/velocityconf
_______________________________________________
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