You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 32 Next »

The information on this page refers to License Statistics v4.12 or newer, which made general improvements to the Usage Per Usage grid. If you are using an earlier version, please refer to the documentation for releases prior to v4.12. 

To see a report on usage per user, select the Usage Per User tab from the Reports page.

The Usage Per User report lets you monitor license usage for a selected type of aggregation to use for the report (described below). With this report, you can change time constraints as appropriate for your needs; for example, you can display license usage information based on monthly usage, but limit the results shown to weeks.

It is worth noting that the Usage Per User report may serve as a warning signal, letting you see the overall trend of license usage based on peak license usage. Therefore, you can consider if the values represent a one-time event or a recurring event that begins to look like a trend.

Types of aggregation

You can specify the type of aggregation by which you aggregate the results for the report. If the aggregation type is not specified, the report will be aggregated by Username and Hostname. Available options are:

Note: The Usergroup and/or Hostgroup options may be disabled, indicating that no groups have been created.

How aggregation is applied in a report

Aggregation enables you to specify detailed levels of the produced results. License usage information can be displayed for a specified entity, letting you juxtapose one set of data with another.


The following diagram shows how License Statistics aggregation options are used by real-world entities in a company.

Types of grouping (time units)

Depending on your needs, you can group feature usage information by the following units of time:

  • Day
  • Week
  • Month
  • Quarter

How grouping by a unit of time works in a report

Grouping by a unit of time lets you group values from specified fields together. For example, license usage information can be limited to a month and within that month displayed based on daily usage. Grouping works in the same way for all other available time units, for any set of selected values.


Let's assume the following values have been returned after grouping feature usage information by Day.

DateHours Used
2014-04-0110
2014-04-0220
2014-04-0430
2014-04-0640

When we choose to group the above feature usage information by Month and set the start date to April 4, 2014, we obtain the following values:

DateHours Used
2014-0470

When we decide to set the start date to April 1, 2014, we get the following values:

DateHours Used
2014-04100

 

Feature Usage Information

The feature usage information includes the following:

Column NameDescription
Date

A particular day or period of time, whose format depends on the selected grouping option.

  1. Day: YYYY-MM-DD; for example, 2014-04-13.

  2. Week: YYYY-MM-DD - YYYY-MM-DD; for example, 2013-11-10 - 2013-11-16 (starts from Sunday).

  3. Month: YYYY-MM; for example, 2014-04.

  4. Quarter: YYYY-Q[1-4]; for example, 2014-Q2.
HostnameA single hostname of a list of hostnames where license usage took place.
UsernameA single username or a list of usernames.
Usergroup NameThe name of a group of users.
Hostgroup NameThe name of a group of hosts.
Hours UsedThe number of hours at least one license of a particular feature was used and/or borrowed.
Hours BorrowedThe number of hours at least one license of a particular feature was borrowed.
Max UsedThe maximum number of licenses used in a particular time period.
Max BorrowedThe maximum number of licenses borrowed in a particular time period.
Max UsageThe maximum allowed level of feature usage, expressed in percentages.


To better understand how possible aggregation scenarios work, let’s look at the following example:

ColumnAggregation TypeScenario
Hours Used/BorrowedUser

In our example, the results shown in the report are limited by Day.

 

Scenario 1 

The user uses 1 license for 8 hours.

Calculation: 8 hours = 8 Hours Used

 

Scenario 2

 

The user uses 2 licenses for 1 hour, then 10 licenses for 2 hours and 1 license for 2 hours.

Calculation: 1 hour  + 2 hours + 2 hours = 5 Hours Used

Max Used/BorrowedUser

In this example, the results shown in the report are limited by Day.

 

Scenario 1

The user uses 2 licenses throughout the day.

 

Calculation: 2 licenses = 2 Max Used/Borrowed

Scenario 2
 

The user uses 2 licenses throughout the day . One license is used constantly for the entire day, while the other one is used only for 1 hour.

Calculation: 2 licenses = 2 Max Used/Borrowed
 

Max UsageUser

In our example, the number of available licenses for a particular feature is 10.

 

Scenario 1

The user uses 2 licenses throughout the day.

 

Calculation: 2 licenses out of 10 licenses = 20%

 

Scenario 2

The user uses 5 licenses throughout the day, but only 2 licenses are used for 1 hour.

 

Calculation: 5 licenses out of 10 licenses = 50%

 

Scenario 3

The user uses 3 licenses throughout the day, but 8 licenses are used for 1 hour.

Calculation: 8 licenses out of 10 licenses = 80% 

Date Range

The Start Date, End Date, and Time Interval fields for which you wish to display license usage are interdependent, i.e. modifying the Start Date field affects the End Date field, depending on the selected Time Interval option. If you select the "Custom" option in the Time Interval options, then both fields (Start Date and End Date) can be modified; however, you will not be able to select the day earlier than the Start Date on the End Date field, and later than the End Date on the Start Date field, because the value on the other field will be automatically adjusted.

  • No labels