Sweet!!, I will certainly have to give that a shot.

 

We will soon have some customers accessing the status of their networks
so we are looking for ways to hide the Nagvis module and other things
but still give them access to their cool NAGVIS maps.

 

So we would have admin, engineer and customer roles with very different
access requirements..

 

Thanks again for the answer to my question.

 

James Whittington

 

From: [email protected]
[mailto:[email protected]] On Behalf Of Rafael
Luis Carneiro
Sent: Wednesday, August 19, 2009 1:17 PM
To: Opsview Users
Subject: Re: [opsview-users] What are valid access roles used
inopsview_web.yml ?

 

James,
You can create a new file called opsview_web_local.yml and make your
changes there.
Copy everything starting at the line that reads "Controller::SideNav:"
on.
I'm only using the admin role to hide/display menus, like this:
[...]
  menus:
    - name: Status
      display: 1
      entries:
        - url:  '/status/hostgroup'
          name: 'Hostgroup Hierarchy'
        - url:  '/viewport'
          name: 'Viewport Summary'
          target: 'viewport'
        - url:  '/cgi-bin/statusmap.cgi?host=all'
          name: 'Network Map'
        - url:  '/status/host?hostgroupid=1'
          name: 'Host Detail'
        - url:  '/status/service'
          name: 'Service Detail'
    - name: Monitoring
      role: admin
      entries:
        - url: '/cacti/graph_view.php'
          name: 'Cacti'
          target: 'cacti'
        - url: '/another/page.php'
          name: 'Another link'
          target: '_blank'
[...]

Rafael

On Wed, Aug 19, 2009 at 1:00 PM, James Whittington
<[email protected]> wrote:

Fellow users of Opsview..

 

We are trying to hide some areas of the Opsview Side Navigation based on
role and I had a couple of questions.

 

We would like many of our support engineers be able to see things like
Nagvis maps,NMIS, and VIEWPORT areas but do not want to make them all
full administrators to do so.

 

In the opsview_web.yml file we see examples of things only visible to
Administrators so it appears we could easily hide things.

We see the keyword "access: ADMINACCESS"  that seems to show/hide side
menu items based on role.

 

Question1: Can we use other roles as well in place of ADMINACCESS?

Question2: Should we edit opsview_web.yml directly or is there an
override file that would survive upgrades?

 

Thanks,

 

James Whittington

VC3, Inc.

 

 


_______________________________________________
Opsview-users mailing list
[email protected]
http://lists.opsview.org/lists/listinfo/opsview-users




-- 
Rafael Carneiro
Computer Engineer

_______________________________________________
Opsview-users mailing list
[email protected]
http://lists.opsview.org/lists/listinfo/opsview-users

Reply via email to