Multi-Tenancy

Configuring Multi-tenancy

This section describes the general method for implementing multi-tenancy in a user environment.

Dependencies

• Devices have been discovered and appear in the Device Catalog.

• Devices are sending event data to an Assure1 collection server.

• Performance data is being collected for a device by an Assure1 collection server.

• Dashboards have been created.

Steps

1. Define the user group(s) and what data should be available to each user group. Consider the following items:

   1. Identify Roles (functionality) in the Assure1 UI that the user group should have access to.

   2. Identify Device Groupings if metric and/or topology information is going to be displayed for the User Group.

   3. Identify Event Groups if events are going to be displayed for the User Group.

      1. Identify Event Menus & Tools that should be available when viewing events.

   4. Identify Dashboard(s) that will be utilized by the user groups, or do new dashboards need to be created.

      1. Identify Dashboard Menus & Tools if they are going to be utilized for a Dashboard associated with the User Group.

   5. Identify internal or external web links or files that should be available to the User Group.

2. Create Device Group to contain all the devices the user group should have access to for all displays.

   1. Configuration -> Device Catalog -> Device Groups.

3. Create Event Filter Group to select all the events the user group should have access to for all displays.

   1. Configuration -> Events -> Filter Groups.

   2. The Group Restriction Filter defines the user groups access to the filter group using text that would be valid in an SQL WHERE clause.

4. Create Dashboard Group to include all the Dashboards that should be available to the User Group.

   1. Configuration -> Dashboards -> Dashboard Groups

5. Create User Group for the identified user community.

   1. Configuration -> AAA -> User Groups.

   2. Assign Permissions, Device Group, Event Filter Group, and Dashboard Group to the User Group.

6. Create Event Menu if the User Group requires the use of right-click menus in the Event List.

   1. Configuration -> Events -> Menus

7. Create Diagram Menu if the User Group requires the use of right-click menus on a Diagram.

   1. Configuration -> Diagrams -> Menus

8. Create Link Group if the User Group requires access to information in the Links.

   1. Configuration -> Links -> Link Groups

9. Test the User Group access by creating a new User or assigning an existing non-Admin User to the User group and logging into the Assure1 UI.

   1. Configuration -> AAA -> Users

Configuring Instance Multi-tenancy

This section covers the process for creating a Virtual Device within the Device Catalog for implementing Instance Multi-Tenancy.

Dependencies

• Devices have been discovered and appear in the Device Catalog.

• Metric data is being collected for these devices and instances on these devices.

Steps

1. Define all the metric instances that should be available to a User Group.

   1. Identify all the devices that should be represented by a Virtual Device.

   2. Identify all the metric instances on the devices that should be represented on the Virtual Device.

2. Create a Virtual Device in the Device Catalog. Set the Device State to Virtual. If the device should inherit characteristics from an existing discovered device, set the Parent Device during virtual device creation.

   1. Configuration -> Device Catalog -> Devices

3. Create Display Instances to assign Metric instances to the Virtual Device by adding a Metric Display Instance for each metric instance to be associated with the Virtual Device.

   1. Configuration -> Metrics -> Display Instances

4. Validate Virtual Device visibility once all Metric Display Instances has been associated with the Virtual Device. The Virtual Device can be utilized similar to any other device in the Device Catalog for establishing the remainder of the configuration for the Multi-tenancy implementation.