Agent Based Licensing Rule

To create an agent-based licensing rule:

Click User Profile > License > License Rules.
Click > Create APM License Rule.
In LICENSE RULE NAME, enter the name of your rule.
In LICENSE ALLOCATION, enter the number of units for each agent module type that this rule allocates.
In the Application Scope tab, select + Specified Applications and select the applications from the list on which you want to apply the license rule. If you don't apply any application scope, the license rule applies to all the applications.
Note:
- Only the agents that report to the selected applications can consume the license units allocated by this rule. You can select one or more applications from the list.
- You can specify a matching criteria to select the applications. If you select Dynamic and then Include dynamic ones, all the dynamic application names matching your criteria are selected for your license rule.
- The agents reporting to the non-matching applications are rejected and cannot report data.
- You can also add un-instrumented applications to the rule in Application Scope so that when you install the agents to instrument these un-monitored applications, they will be allowed to consume licenses defined in this rule.
- You can select up to 100 applications to assign to a rule.
In the Server Scope tab, select + Specified Servers and select the servers from the list on which you want to apply the license rule. If you don't apply any server scope, the license rule applies to all the servers.
Note:
- Only the agents deployed on the selected servers can consume the license units allocated by this rule. You can select one or more servers from the list.
- You can specify a matching criteria to select the servers. If you select Dynamic and then Include dynamic ones, all the dynamic server names matching your criteria are selected for your license rule.
- The agents reporting to the non-matching servers are rejected and cannot report data.
- You can also add un-monitored machines in Server Scope so that when you install the agents to instrument these un-monitored servers, they will be allowed to consume licenses defined in this rule.
Click Done to create the license rule.

This diagram is an example of a scope configuration.

Agent based license scope configuration

Return to the default rule and decrement your unit allocation by the number of units that you allocated in your custom rule. Otherwise, the allocations will show as over-provisioned.

Note: You must allocate the same number of Machine Agents as your APM Agents. For example, if you allocate 10 Java Agents, 10 .NET Agents, and 10 Node.js Agents, you must allocate 30 Machine Agent units. For each rule you create, a new access key is generated, and the agents under that rule are authenticated with that generated key. Update your agent to use this new access key and restart the agent.

Best Practices


Action	Recommendation
Create License Rules	When you create license rules, follow consistent criteria for selecting which applications belong to a rule. We recommend: If you want a rule to contain multiple applications, then group applications by business unit. If you want to view individual application usage, then select only one application per rule.
Delete a Default License Rule	Splunk AppDynamics does not recommend deleting default license rules. Instead, we recommend changing all of the license entitlements to 0. Warning: If you do delete a default rule: If there is only one license rule (for example, the default), deleting it will take the License Management UI back to a state when license rules never existed. Deleting a license rule will not impact existing agents because they will start reporting using the account-level access key. If you have multiple license rules (one default and multiple custom) and you delete the default rule, you will not be able to recreate it until you delete all other rules. Click Create Rules to create a new default rule. The access key will be different and you will also need to re-configure your agents.
Delete a custom license rule	Deleting and recreating a custom license rule will not retrieve the old access key, even if you use the same name, since access keys are generated dynamically at runtime.