At AppSphere 2016, we gave attendees a glimpse into the future of our new license management system. As we continue to grow in large enterprises and gain broader adoption across more parts of the organizations we service, our customers have asked us to help their administrators manage license entitlements more easily.
Imagine the challenge of allocating licenses across tens of thousands of application nodes for operations teams in different business units located in various parts of the world. Without the right tools, planning and predicting license utilization can quickly become tedious and time consuming.
In building a reimagined enterprise-grade license management system, we focused on ease of use, scalability, and configurability. In our demo at AppSphere 2016, we showed off a few key areas of focus.
License Usage Visualization
Figure 1: Peak license usage across agent modules over the past four hours.
In the newly designed license usage page, admins can see organization-wide license utilization across all agent modules in a single view. As you can see in Figure 1, we’ve selected .NET, which pops up a more detailed usage chart. When we switch the time range to a different period, all associated charts update in real-time.
Our platform is able to measure license consumption over time down to minute granularity. This is extremely useful for customers with highly volatile traffic patterns.
License Entitlements and Rules
Figure 2: Different teams can be assigned different access keys.
A large financial institution may have different teams focused on institutional banking, commercial banking, and compliance, for example. Each team has different needs in terms of technology. In our license management system, we’re able to create rules which allow you to allocate a pool of licenses for each team and get a real-time view into how these licenses are being utilized. We’ve also made it a lot easier to move licenses between teams or between agent modules.
Figure 3: Entitlement settings allow users to allocate licenses for different agent modules.
Once a rule is created, an access key is generated. This access key can be shared with members of the team for application instrumentation.
Figure 4: Application Scope and Machine Scope can be added as part of a rule to automatically include applications or machines that match a set of criteria.
As part of rules, we’ve added a powerful capability called Scopes, which allows admins to automatically apply rules to specific applications or machines by using regular expressions and naming conventions.
For example, if we have applications for user testing, we can prefix all of these applications with “user_test” and match this prefix as part of a scope. This applies equally to machines as well, so only machines named “user_test” will consume licenses. All of these features are critical for large enterprise deployments and make it easy for admins to manage their licenses.
To test drive some of these features and more, sign up for a free trial.