Multi User Installation

[samer]

Hello,

I resell hosting packages, I want my customers to be able to loin and add their domain to monitor, and choose the service port they will monitor

Every user is completely independent and isolated than others, is that possible with Zabbix

Thankx in advance

Kind Regards
Samer

[Alexei]

Yes, you may restrict permission so that an user will have access to his own hosts only. In 1.4 we are introducing multi-institution support, it means that one ZABBIX server will be able to monitor several environments and all environments will be completely separated one from another in ZABBIX.

[schneck]

Yes, you may restrict permission so that an user will have access to his own hosts only.

Currently, the only way I've figured out to allow a user access to her own hosts is to enumerate each and every host, one per ACL line. This is quite tedious if we're talking about 100s of hosts.

Is there a way to do it eg. by host group?

In 1.4 we are introducing multi-institution support, it means that one ZABBIX server will be able to monitor several environments and all environments will be completely separated one from another in ZABBIX.

This sounds great!

Thanks,

\B.

[Alexei]

Is there a way to do it eg. by host group?

Currently it is not possible. In ZABBIX 1.4 we are switching to more simple user permission schema which will work on host group level as well.

[IT_Architect]

Currently it is not possible. In ZABBIX 1.4 we are switching to more simple user permission schema which will work on host group level as well.

Is there any way to give each user his own database to accomplish that?

[Klug]

Is there any way to give each user his own database to accomplish that?

Giving each user his own database means several non-interacting Zabbix installations, doesn't it ?

[IT_Architect]

Giving each user his own database means several non-interacting Zabbix installations, doesn't it ?

Exactly what is intended. It sounded initially like an easy work-around but the more I think about it, the uglier it sounds.
Either:
1. The daemon opens multiple connections to different databases, zabbix1, zabbix2, etc. and cycles through them. It would also require a notification mechanism to alert it to an added or removed database.
2. Multiple copies of the daemon run, each initialized to work with a specific database. Then you need to provide a mechanism to start a deamon for new databases and remove them for databases no longer present.

It would be actually be easier to add groups that contain users and servers. The user's rights can be granted as they are today, and the group could filter the servers visible to the members of the group. There would be a built-in admin group that could see all servers. That actually should be rather easy to implement and provide a huge advantage in usability.

[Klug]

the more I think about it, the uglier it sounds.

Agreed 8)

This can easily been done simply by setting up several instances (as I said), with several websites and databases (and launching several daemons).

But that's very far from a true "multi user" setup (single web interface, single daemon).