[ZBXNEXT-59] Multi Tenant Enable IT Services Created: 2009 Aug 27  Updated: 2021 Oct 13  Resolved: 2021 Oct 13

Status: Closed
Project: ZABBIX FEATURE REQUESTS
Component/s: Frontend (F)
Affects Version/s: None
Fix Version/s: None

Type: New Feature Request Priority: Major
Reporter: Mike Cotrone Assignee: Unassigned
Resolution: Fixed Votes: 76
Labels: itservices, patch, permissions
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified
Environment:

Ubuntu 8.10
Zabbix 1.6.5


Attachments: File 0001-Prune-the-IT-services-tree-of-nodes-with-no-triggers.patch     Text File username-filtering.patch    
Issue Links:
Duplicate
is duplicated by ZBXNEXT-6787 User permissions for the service tree Closed
is duplicated by ZBXNEXT-4971 Is there any way to restrict the view... Closed
is duplicated by ZBXNEXT-6203 Show only the services of the hosts i... Closed
is duplicated by ZBX-16034 Services SLA Page visible to all users Closed
is duplicated by ZBX-4582 it services (SLA) are accessible by e... Closed
is duplicated by ZBX-16977 IT Service User/Group Permissions pro... Closed

 Description   

We are using Zabbix in a multi-tenant environment and would love the ability to have the "IT Services" be tied to the user group for multi-tenant. Many users find this feature very useful and unique and in a multi tenant environment can be very useful.



 Comments   
Comment by Mike Cotrone [ 2010 Dec 21 ]

We are now on 1.8(3) w/ Ubuntu 10.04 and we still would love this functionality.

Comment by richlv [ 2011 Sep 26 ]

i'm assuming this is about access permissions on it services

Comment by Igor Danoshaites (Inactive) [ 2011 Sep 26 ]

Mail from Mike Cotrone to [email protected]:

Yes multi group level access. Thanks!

Comment by Åsmund Grammeltvedt [ 2011 Oct 31 ]

Added suggested patch for pruning the service tree.

I just realized that this doesn't work if you want to define services in the web interface, since it will hide any nodes that haven't got any children, making it hard to add children to the newly created (and now hinden) ndoe.

Comment by Maarten Vink [ 2011 Nov 08 ]

A way to hide/show specific IT services based on the user's group would be much appreciated. This could easily be tied into the current permission scheme by only showing IT Services for which the logged in user has permissions to access all of the underlying triggers.

Comment by Jonathan Vargas [ 2015 Mar 31 ]

I face the same issue. I define an TI hierarchy as follows:

  • root
    _ Organization A (not associated with trigger, nor calculated)
    __ Service A-1
    __ Service A-2
    __ Service A-3
    _ Organization B (not associated with trigger, nor calculated)
    __ Service B-1
    __ Service B-2
    __ Service B-3
    _ Organization C (not associated with trigger, nor calculated)
    __ Service C-1
    __ Service C-2
    __ Service C-3

Currently:

Users that monitor hosts at Organization A, are able to see "Organization B" and "Organization C" in the hierarchy, but not their children with triggers assigned.

Expected:

We would like to hide at all higher levels too, so that user that monitor Organization A, don't see Organization B and Organization C levels at all, if it's unrelated with them.

Proposal:

By default, hide all higher levels in the hierarchy to everyone, unless there is at least one trigger in its sub-hierarchy where the user has permission to read.

Another alternative would be to add a separate assignment of permissions per IT Service

Comment by Gareth Brown [ 2015 Apr 27 ]

Bump. Not sure if this is really a feature or whether it is a bug in permission structure TBH

Comment by orogor [ 2015 Nov 27 ]

working patch as of 2.4.7
http://balaioti.blogspot.fr/2013/12/zabbix-multi-tenant-it-services-working.html

Comment by jj [ 2015 Dec 03 ]

yep, this one is strange, can't use it services if we want to share some zbx user logins ;[

Comment by Gareth Brown [ 2015 Dec 03 ]

There is a hack to do this but it's not ideal. We created a branch from root called Services, then created individual SLAs specific for each tenant user. All these SLAs created must have a trigger assigned to them and that trigger must be linked to a host that only the required users have permissions for.

It is also worth noting that Maps and Screens are also subject to the same disfunction. Therefore, you must have no screens with zero elements (they will show in the drop-down menu) and no maps without host or triggers in the same manner as above.

Comment by Leandro Ferreira Rocha [ 2016 Mar 04 ]

We are now on 3.0.1 and we still would love this functionality.

Comment by Jim Druce [ 2016 May 16 ]

Can please also echo i plea to implement this functionality this is a great feature in Zabbix but i really only want users to see their own data not everything in IT services..

Comment by Luciano de Carvalho [ 2017 Feb 14 ]

We're on 3.2 and we will love this functionality to be included in Zabbix!

Comment by Jordi de Wal [ 2017 May 22 ]

Would love to see user / user group restrictions for IT services implemented

Comment by dimir [ 2017 May 22 ]

Thanks. We will see if we can get this into 4.0 .

Comment by Pascal Uhlmann [ 2017 Aug 03 ]

We also need to restrict our customer users to see only their own IT services. As we're using Zabbix 3.0 it would be nice if it would be implemented also in this version.

Comment by Marc [ 2017 Aug 03 ]

pu,

this is quite unlikely to happen for an already released version. However, might be worth to get in touch with sales at zabbix dot com.

Comment by Mehmet Ali Buyukkarakas [ 2017 Aug 28 ]

We need this feature. Hope to see in next big release.

Comment by Antti Hurme [ 2018 Jan 23 ]

Any update from Zabbix if this will be changed? Would be nice not to manually patch this.

Edit: One option could be to create custom views and use similar permissions setup as dashboards now have with public/private.

Comment by AndreaConsadori [ 2018 Feb 20 ]

please fix it, is a must ..

Comment by Juliano Romani [ 2018 Mar 28 ]

When will it be enter in the roadmap?

Comment by Marc [ 2018 Mar 29 ]

ca6eca, likely not before (co-)sponsoring its development .

Comment by Cesar Murilo da Silva Junior [ 2019 Jan 22 ]

Will the SLA restriction per user be implemented?

Comment by Celio di Cavalcanti [ 2019 Jan 24 ]

Please inform if possible the roadmap for this fix.

Is there any workaround?

Comment by Andre Fernandes [ 2019 Feb 15 ]

Please informe if this will be implemented or if exists any workaround.

Comment by Mehmet Ali Buyukkarakas [ 2019 Feb 15 ]

Agree. It's very important when we work with multiple customers. Please inform us.

Comment by dimir [ 2019 Feb 18 ]

Unfortunately I couldn't get an approve that it is going to be part of 4.4 . If there is an urge, as mentioned in comments above, someone needs to take the leadership of co-sponsoring this development and request the quote from the Sales team.

Comment by Celio di Cavalcanti [ 2019 Mar 08 ]

Dear Dimir,

The problem was detected in version 1.6, so I believe there was already investment to solve it.

I respect your suggestion, but that's my opinion.

Tks,

Celio di Cavalcanti

 

Comment by Cesar Murilo da Silva Junior [ 2019 Mar 08 ]

I agree with Celio.

Comment by Andre Fernandes [ 2019 Mar 12 ]

I agree with Celio.

Comment by dimir [ 2019 Mar 12 ]

Look, I'm not a decision maker what goes into release. I was trying to get some attention to this issue and provide you with some input. I was told, there are more top-voted feature requests out there, waiting to be implemented. The "Votes" matter.

Comment by Alessandro Lombardi [ 2019 Apr 23 ]

I have now voted. Please add this feature, many MSP use zabbix and this is a TOP feature!

Comment by dsm team [ 2019 Jun 04 ]

Voted as well.

Comment by Frédéric Beuserie [ 2019 Aug 05 ]

I implemented a quick workaround, perhaps he can help someone.

there is two prerequisite:

  • username for your customer access as some kind of information (for me it's always 'cust-xxxx' for exemple, xxxx depending of the customer
  • second level of the tree is named to match the customer who need access: for exemple i've x second level nodes with name like 'cust-xxxx, cust-yyyyy, cust-zzzz, ...'
  • then the small snippet below simply check if the current logged in user start with 'cust-' (it's customer access), then if the xxxxx parts match between the user and the second level node.
    • if it match, the node and all childs are displayed
    • if it doesn't match, the node and all childs are filtered
  • if the username doesn't starts with 'cust-', then nothing is done (admn and internal access)

 

see attached patch (username-filtering.patch)

Comment by Ognjen sijan [ 2020 Mar 09 ]

This is a working solution as someone has already posted. i am using it in 4.4.6 and it works well. 

http://balaioti.blogspot.fr/2013/12/zabbix-multi-tenant-it-services-working.html

My SLA is structured as group then one level down devices in the group and next level down triggers for the SLA

The only thing i changed in the above link was to comment out the line below. As this prevents a weird printout at the top of the screen above the Services headline.

#print_r($children['servicedownid']);

 

 

Comment by Jan Paul [ 2020 Sep 22 ]

Thanks for the link to the blog. This helps me a lot.

Now I only need to use the API interface to mass insert services/trigger. 

Comment by Heitor Batista de Oliveira [ 2021 Jan 21 ]

Hello Zabbix! Sorry to brother you but this feature is very, very important for us.

Please!, input this feature on roadmap.

 

Thank you in advance!

Comment by Alexei Vladishev [ 2021 Apr 28 ]

Hey all! We are working on massive improvements for service-related functionality. Support of user permissions for services is part of it. The functionality is planned to be delivered in Zabbix 6.0 LTS by the end of this year.

Comment by dimir [ 2021 Aug 06 ]

Looks like ZBXNEXT-6787 will implement this one.

Comment by Alexei Vladishev [ 2021 Oct 13 ]

This functionality was implemented under ZBXNEXT-6787 and available in 6.0.0alpha3 and later releases.

Generated at Wed Apr 24 00:05:07 EEST 2024 using Jira 9.12.4#9120004-sha1:625303b708afdb767e17cb2838290c41888e9ff0.