Multi-Tenant Controller Accounts

This page describes how to create and manage accounts in a multi-tenant Controller. The tenant mode determines whether the Controller UI offers single or multiple environments. See Controller Deployment.

Switch from Single-Tenant to Multi-Tenant Mode

Warning: Switching from single-tenancy to multi-tenancy mode is supported. However, switching from multi-tenancy to single-tenancy is not. Take precautions to ensure multi-tenancy is the correct mode for your environment.

If multi-tenancy is enabled for an on-premises Controller, users must enter the account name in the Account field when logging in to the Controller UI.

  1. Navigate to the Administration Console.
  2. Locate the multitenant.controller setting.
  3. Set the value to true .

Create Accounts in Multi-Tenant Mode

In multi-tenant mode, you can add accounts as follows:

  1. Log in to the Administration Console as the Splunk AppDynamics root user.
  2. Click Account Settings and then Add.
  3. Define the licensing entitlements that apply to the account.
    Account-level license unit limits let you prevent a particular account from using more licensing units than it should. You can view the total license units available through Settings Settings > Admin > License. See Observe License Usage.
    Note: The overall license limits applicable at the Controller level are independent of any specific limits you apply at the account level.
    Agent-based Licensing: For example, if an account is set up with a Java Agent limit of 100, you can ensure that the new account never interferes with the license availability of another account by setting the Java Units Provisioned value for the account to a much smaller limit. However, if you set it to 100 and other accounts are also set to that amount, the first 100 agents that connect to the Controller would occupy those units, regardless of the accounts they report in to. Similarly, you can limit the lifespan of the account by setting an expiration date for the license. Infrastructure-based Licensing: For example, if an account is set up with an Infrastructure Monitoring limit of 100, you can ensure that the new account never interferes with the license availability of another account by setting the Infrastructure Monitoring value for the account to a much smaller limit. However, if you set it to 100 and other accounts are also set to that amount, the first servers with CPU cores totalling up to 100 would occupy those units, regardless of the accounts they report in to. Similarly, you can limit the lifespan of the account by setting an expiration date for the license.
  4. When finished defining entitlements, click Save .
After enabling multi-tenant mode, users must specify the account they want to log into in theAccountfield in the Controller UI login screen. See: