Points to Consider

  • For each license rule you create, a new access key is generated, and the agents under that rule are authenticated with that generated key. Make sure to update your agent to use this new access key and restart the agent.
  • Make sure the selected applications and servers on each rule are an exclusive list and are not part of multiple rules. This structuring helps with managing chargebacks effectively.
  • If you choose not to create any rules, then your license allocation follows the default rule, which allows all applications and servers to equally consume each license.
  • To simplify license reporting in a cluster (containerized environment), we recommend that all applications and agents use the same license key when using license rules.
  • When configuring rules, you can allocate more units than you were originally provisioned by Splunk AppDynamics. Over-provisioning units buffer your unit allocation and are useful when the exact number of license units for the list of applications and servers for the rule are unknown. Although the allocation on the rule is unbounded, Splunk AppDynamics limits your unit usage according to the number of licenses you purchased.
Warning: Overlapping configurations on license rules may complicate license reporting. Splunk AppDynamics recommends you configure license rules with caution because you must confirm the license usage on each rule matches the license usage at the account level. License usage at the account level is the union of usage for all license rules, and not a sum of usage of all license rules. When multiple applications are hosted on the same host and each application agent uses a different rule key, usage will be reported in both the rules, and it will be reported as if you are consuming double the licenses, which is incorrect.