5.11 Tenant configuration

In a multi-tenant configuration equipments belonging to different customers are monitored with the same PVSR instance and users of these customers view data relevant only to their equipments. There are three aspects of such a scenario:

·       User access: each user should only see data for his equipments. The authorization in this case is not different from any other PVSR installation, i.e. separate users must be created and each of them should only have access to the correct set of equipments. This configuration must be done in the “User and group rights” menu, since this is in no way different than any other authorization setup. In other words: users cannot be associated with tenants in the PVSR database

·       Data collection: each tenant should have its own separate data collector groups, so that the data collection of different tenants do not interfere with each other

·       Reporting and threshold processing: it is recommended that each tenant have its own processing components, for the same reason as above

The tenant configuration page is there for the second and third points. When adding a new tenant to the system, the administrator has to create at least one threshold and one report processing module for it and should select its data collector groups created before the operation. If needed event processing modules can also be created (SNMP trap / syslog). Unlike in the non-tenant mode, each tenant can have more than one report and more than one threshold processing modules. It is important to note that modules need to be created or deleted on the tenant configuration page, but they has to be modified like any other module: on the server configuration page. It is recommended for each tenant to have at least one report and one threshold processing module, but this isn’t required.

The systems assigns the thresholds and report variables to tenants in different ways:

·       Normal thresholds: each threshold can contain multiple measurements and so each threshold can be associated with multiple equipments and collector groups. If for a threshold each collector group belongs to the same tenant and the tenant has threshold processing module then the system will automatically assign one of the tenant’s threshold processing module to the threshold. Otherwise the the regular central threshold processing module will do the evaluation

·       Group thresholds: each group threshold has an optional tenant parameter

·       Report variables: each report variable can belong to one report server. If the tenant has report processing modules then separate report variables can be created for the tenant. Otherwise the report calculation is done by the central processing module

The recommended steps to add a new tenant are these:

1.      Optionally install new servers for PVSR

2.      Create new collector groups and collectors

3.      Create new tenant with these collector groups

4.      Add new sites for the tenant by assigning to them one of the new collector groups

5.      Create new user who have access only to those sites

6.      Create/import/enable new reports with the new tenant selected

7.      Create the equipments for the new tenant

The tenant configuration page shows the tenants in the system, with the status indication of all of their server modules (collectors and report/threshold/event processing), collector groups and processing module names. There are several links for each of the tenants besides the usual [edit] and [del]. These takes the user to the status, event, watchdog and search pages with the tenant selected. On the edit page the administrators can add new threshold/report/event processing modules and select the tenant’s collector groups (this is a multi-select field).