PDFs

On this page:

Related Pages:

Your Rating:
Results:
PatheticBadOKGoodOutstanding!
46 rates

The AppDynamics license that you purchase determines the features and deployment scale available to you. A license file that applies to your entire platform resides on the Controller. You do not need to install a license file for other components, such as on the agents or with the on-premises EUM Server, for example.

There are two different types of AppDynamics Licenses: Pro and Lite. You can try the Pro license free for 15 days. When the free trial ends, the license converts to a Lite license, as described in Lite and Pro Editions.

When you purchase Application Performance Monitoring licenses, you can create rules to fine-tune license distributions across your organization. 

Permissions

Users must have a role with the View and Configure Licenses permission for this activity.

License Management Scope

The App iQ Controller uses licensing to determine the features that are licensed and available in an App iQ deployment and the scale of the deployment. The License Management module provides visibility into your license consumption model, allows you to manage entitlements from your license pools, and manage and distribute your access keys usage so you can scale out your different applications.

The following illustrates the flexibility of license assignments under the license scope configuration model.

 

License Management Scope configuration allows you to assign licenses to specific applications and machines. Using scopes to configure licenses allows you to express and scale the configuration modules as required.

License Management provides:

  • Granular control with precise rules and access keys to restrict which hosts and apps consume licenses
  • Great visibility with detailed current and historical usage reporting across business units and services

On the Add and Edit Rule dialogs, you can create or edit rules to specify license allocation according to selected agents, applications, and machines/servers, following a mix and match model. For example, a rule can be applied to a selected application running on several specific machines. 

Viewing License Information

To view license information in the Controller UI, click the gear icon  and choose License.

The License dashboard consists of three tabs:

  • Account Usage: displays the maximum license usage in the time range you specify
  • Rules: allows you to configure license allocation across machines and applications
  • Account: displays the account name, access key, and expiration

The following sections cover each of the tabs in more detail.

Viewing Account Usage

In the Account Usage tab, you can view the number of licenses consumed and license expiration dates for the following product areas:

  • Applications: Java, .NET, C/C++, Apache, PHP, Node.js, Python, Go
  • User Experience
  • Databases
  • Server Visibility
  • Network Visibility
  • Analytics

You can click on each application type to see that type's license usage. You can specify the time range that you want to see data for in the drop-down menu on the upper right.  For more information about how AppDynamics defines license units for each product module, see License Entitlements and Restrictions

For Analytics, the graph shows the cumulative license usage over the time period you specify, even though the license usage count is reset daily. To see your license usage for one day, set the time range to 23 hours and 59 seconds.

Creating Rules

In the Rules tab, you can create rules to specify the number of Application Performance Monitoring licenses to allocate to specified applications and machines. If you choose not to create any rules, your license allocation follows the default rule, which distributes the licenses evenly across all applications and machines.

In a rule, you can specify the following allocation details: 

  • How many units you want to allocate to each rule
  • Which applications are allowed to consume the units (agents) allocated by this rule
  • Which servers are allowed to consume the units (agents) allocated by this rule

When license rules are enabled, you must ensure that all your units are accounted for by either the default rule or a custom rule. AppDynamics follows a mix and match model: you can adjust the number of units allocated to each license rule at any time.

Create a Custom Rule

  1. Click the gear icon  and choose License.
  2. Enable the license rules feature by clicking Create Rules on the Rules tab.
  3. Click +/Create to display the Add Rule dialog box.
  4. In the General tab, enter the name of your rule and the number of units for each agent module type that this rule allocates. 
  5. In the Application Scope tab, select Specified Applications to restrict which applications agents can report to. 
    Only agents that report to the applications you specify can consume the units allocated by this rule. You can select one or more applications from the Available Applications list and click the left arrow button to move the applications to the Selected Applications box. You can specify matching criteria for allowed applications by clicking Add. You can also specify matching criteria for applications that you have not yet created. The applications you specify using matching criteria will not appear in the Selected Applications box. You can select up to 100 applications to assign to a rule.
  6. In the Server Scope tab, select Specified Servers to restrict which servers agents can be deployed to. 
    Only agents deployed on the servers you specify can consume the units allocated by this rule. You can select one or more servers from the Available Servers list and click the left arrow to move the applications to the Selected Applications box. You can specify matching criteria for allowed servers by clicking Add. You can also specify matching criteria for servers not yet monitored by AppDynamics. The applications you specify using matching criteria will not appear in the Selected Applications box.
    Using the Also include applications/servers matching the following criteria option, you can select applications and servers by matching multiple machines using the match criteria. This is more efficient than scrolling through thousands of applications and machines to make your selections manually. 
    You can also add uninstrumented applications to the rule in the Application Scope and unmonitored machines in the Server Scope, so that when you install the agents to instrument these unmonitored applications and servers, they will be allowed to use the licenses defined in this rule.

After You Create a Rule

After creating your custom rule, 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.

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.

You must allocate the same number of machine agents as your APM agents. For example, if you allocate ten Java agents, ten .NET agents, and 10 Node.js agents, you must allocate 30 Machine Agent units.

Viewing License Usage

To view license usage for the units allocated by a rule, click the rule. AppDynamics indicates license usage percentage by color:

  • Blue: under 80% units used
  • Yellow: over 80% units used
  • Red: 100% units used

Over-provisioning Units

When configuring rules, you can allocate more units than you were originally provisioned by AppDynamics. Over-provisioning units buffer your unit allocation and is useful if you are unsure which agent type will consume more units. While your unit allocation is unbounded, AppDynamics limits your unit usage according to the number of licenses you purchase. In other words, AppDynamics continues to reports data for over-provisioned units as long as you have the units available, such as when the license usage for certain agents is lower than expected.

If a Licensed Agent cannot Register with the Controller

If a licensed agent such as a Server Visibility cannot register with the Controller, do the following:

  • Check that the user account has a product license for the relevant agent type. 
  • If the user account has license rules defined, make sure these have the correct number of license units allocated. To change the number of allocated units in a rule:
    1. Go to Controller Settings (gear icon > License > Rules.
    2. Edit the License Rule of interest. (There might be only one License Rule, named Default.)
    3. In the General tab, set the Allocated Units field for the relevant license and apply the change.

License Rules Best Practices

When creating license rules, you may want to follow consistent criteria for selecting which applications belong to a rule. We recommend that you follow one of these criteria:

  • Group applications by business unit. If you want a rule to contain multiple applications, select applications that belong to the same business unit.
  • If you want to view individual application usage, select only one application for a rule.

Viewing Access Keys

On the Account tab, you can view your license type (Pro or Lite) and access key. You use the access key to connect agents to the Controller. See Agent-to-Controller Connections.

  • No labels