#
LicenseAnalyzer™ - Level 2 (True Active Usage) Data Types
#
Unix Pacct [0]
This data type contains process accounting (pacct) data generated by the system kernel. All Unix systems have built-in process accounting, and Open iT uses its output, converts it to the Open iT format, then saves it in a database. The Unix Pacct data type is well-suited to measure who runs what and where and when it is run. The CPU or memory usage may be calculated, and the number of times the programs are run may be counted.
#
Classifications
#
Measurements
#
Unix Application Usage [32]
Information about jobs executed under the acc-wrapper is found here. This data type resembles regular Unix process accounting. The difference is that acc-wrapper provides the total usage of resources by the command itself and its subprocesses during the command's runtime.
If a command forks off child processes, each will be accounted for separately under Unix process accounting. On the other hand, the acc-wrapper provides one entry for the complete process tree created and finished during the command's runtime. This means that the daemons, which detach from the tty by making a subprocess and the command itself exits, will not be accounted for properly. Accounting for these must be done by Unix Pacct.
#
Classifications
#
Measurements
#
Extended Pacct [54]
This data type extends to the regular process accounting (pacct), which is intended for accounting on long processes/jobs, and providing information on accumulated and average resident set sizes (RSS).
#
Classifications
If the data is based on pure ps, the exit status will always be 0 regardless of the actual exit status because ps does not give any exit status.
#
Measurements
If the source is ps only, the virtual memory is used instead of the pacct memory value. If the source is ps and pacct, the virtual memory is used instead of the pacct memory only if the pacct memory values seem to have wrapped.
#
UsageAnalyzer Break [56]
A break is a period when someone is running the computer but not using the mouse or keyboard. This starts immediately after the last mouse or keyboard event and lasts until the next event. However, inactivity shorter than five seconds is not considered a break.
#
Classifications
Break durations will be reported only for active application windows where there are no keyboard and mouse activities.
#
Measurements
#
UsageAnalyzer Work [57]
This data type reports on user activity on the keyboard and mouse while using an application. It is reported as time - period lengths and totals. The UsageAnalyzer Work data type can also be defined as a period of keyboard and/or mouse events, where the gap in time between each event is less than a configured value which is five seconds by default.
This data type can also indicate the intensity of application usage, profile licensed software, and see the extent of use of a GUI-based application.
#
Classifications
#
Measurements
Period average and Period max will be accurate if the report resolution is one day or more.
#
UsageAnalyzer Events [58]
This data type reports on the events consisting of keyboard keypress, mouse click, mouse wheel rotation, and mouse movement.
#
Classifications
Labels for keyboard event type are sorted alphabetically in reports.
#
Measurements
#
License Optimizer Use [62]
This data type provides an overview of application disable status at the host and user levels, whether the application is in an enabled, disabled, or interactive request (IRQ/wait) status. It also provides information such as application binary name with path.
#
Classifications
#
Measurements
#
License Optimizer Events [64]
This data type provides an overview of events associated with an application being monitored, for example, the number of keyboard activities per second or the CPU loads per second.
#
Classifications
#
Measurements
#
License Optimizer Total Use [70]
This data type provides an overview of how long an application has been running for the given period.
#
Classifications
#
Measurements
#
Process Accounting [87]
Process Accounting logs the same processes as Pacct and Extended Pacct. However, it logs periodically, generating data every hour for every process.
#
Classifications
#
Measurements
#
License Optimizer Actions [92]
This data type provides an overview of the number of times an application has undergone various optimization stages, such as terminated, suspended, logged, etc.
#
Classifications
For the Action classification, Quit means that the application was terminated by the user while Terminate means that the application was terminated by LicenseOptimizer itself.
#
Measurements
#
OLAP Freeze Raw Hourly [97]
This data type provides an overview of featureset application usage.
#
Data Fields
#
License Optimizer Individual Usage [98]
This data type provides an overview of application disable status at the user level.
#
Classifications
#
Measurements
#
License Optimizer Usergroups [99]
This data type provides an overview of how an application has been running for the given period at a group level.
#
Classifications
#
Measurements
#
Web App Browser Log [120]
This data type provides an overview of the historical usage of all the configured web applications from web browser logs.
#
Classifications
#
Measurements
#
Web App Proxy Log [121]
This data type provides an overview of the historical usage of all the configured web applications from web proxy logs.
#
Classifications
#
Measurements
#
Web App Browser Activity [122]
This data type provides an overview of the historical usage of all the configured web applications from web browser plugin cache.
#
Classifications
#
Measurements
#
Web App Total Use [123]
This data type provides a total overview of the historical usage of all the configured web applications from web browser logs.
#
Classifications
#
Measurements
#
Freeze Feature Usage [141]
This data type provides additional details regarding features and feature versions for reporting on Level 2 applications.
#
Data Fields
1. The application was in waiting to get user response to be disabled or to continue to work.