Hi Everyone!
Right now, we have 1 team that manages the Zabbix estate, this has been primarily been the Linux team, as we have used that to monitor all of the Linux systems and the systems on them. We have happily been using this like this for quite some time, all of us being super admins and granting various teams access to read their own hosts, alerts, create dashboards etc.. all going well! They only see what they need and can handle the problems themselves.
Senior management across the group have now (finally!!) seen the benefits of this and now want to expand to other teams, such as the Windows administrators, Networks teams, virtualisation etc.
I'm expanding out the Zabbix installation so that we can allow various admins within these teams to be able to manage their own systems. The problem is, I cannot get the permissions to work such that the can create their own groups or templates, we have to create them for them. All the other items is fine - creating hosts, trigger actions, auto registration.. everything like that.
I found that the code is strictly limited to "USER_TYPE_SUPER_ADMIN" in https://git.zabbix.com/projects/ZBX/...group.list.php
If I grant them Super Admin roles, they now see the entire estate and, quite frankly, they will just see noise from all of the other teams and no one wants that.
What I'm looking at now is that this is almost like an MSP type configuration. I'm posting this into the Large Environments as I'm hoping that some of you have come across this use case before. By the time we're finished, I expect us to be looking at around 6000+ hosts up from around the 1000 hosts as we will continue to separate out the applications to the teams. Such as Server OS, MSSQL, MySQL, Oracle, Postgresql, AD Controllers, distinct Docker Instances, NGINX, IIS, Firewalls, Proxy Systems, etc)
Any thoughts and guidelines appreciated!
Cheers,
Sven
Right now, we have 1 team that manages the Zabbix estate, this has been primarily been the Linux team, as we have used that to monitor all of the Linux systems and the systems on them. We have happily been using this like this for quite some time, all of us being super admins and granting various teams access to read their own hosts, alerts, create dashboards etc.. all going well! They only see what they need and can handle the problems themselves.
Senior management across the group have now (finally!!) seen the benefits of this and now want to expand to other teams, such as the Windows administrators, Networks teams, virtualisation etc.
I'm expanding out the Zabbix installation so that we can allow various admins within these teams to be able to manage their own systems. The problem is, I cannot get the permissions to work such that the can create their own groups or templates, we have to create them for them. All the other items is fine - creating hosts, trigger actions, auto registration.. everything like that.
I found that the code is strictly limited to "USER_TYPE_SUPER_ADMIN" in https://git.zabbix.com/projects/ZBX/...group.list.php
If I grant them Super Admin roles, they now see the entire estate and, quite frankly, they will just see noise from all of the other teams and no one wants that.
What I'm looking at now is that this is almost like an MSP type configuration. I'm posting this into the Large Environments as I'm hoping that some of you have come across this use case before. By the time we're finished, I expect us to be looking at around 6000+ hosts up from around the 1000 hosts as we will continue to separate out the applications to the teams. Such as Server OS, MSSQL, MySQL, Oracle, Postgresql, AD Controllers, distinct Docker Instances, NGINX, IIS, Firewalls, Proxy Systems, etc)
Any thoughts and guidelines appreciated!
Cheers,
Sven
Comment