Searching...
Filters
SmallMediumLarge
Home Print Show Topic URL Previous Next
IT Management Suite
Client Management Suite
Server Management Suite
Deployment Solution
Asset Management Suite
ServiceDesk

Application summary data

Inventory Solution

Application metering is only available on Windows computers.

Each time a metered application starts, Application Metering Plug-in records application summary data. This data is stored on the managed computer and sent to the CMDB at the end of the application monitoring period. If any data was sent during the monitoring period, it is replaced at the end of the monitoring period.

Application summary data is sent to the CMDB in batches daily by default for the following types of applications:

  • The applications that are associated to the software components of the software products, for which the software-based usage tracking option is enabled.

    You can view this data in the Executable Usage and Underutilized Software reports.

  • The applications that are defined and marked as allowed or denied in a turned on application metering policy.

    You can view this data in the Executable Usage report.

See Viewing inventory data in reports

To prevent an overload to the system when this data is sent, the data is randomly sent over an interval of time. A value in the HKEY_LOCAL_MACHINE\SOFTWARE\Altiris\Application Metering registry key on each managed computer determines the length of the interval. The name of the value is Fuzzy Factor, and it is set to 10 by default. This value specifies the time interval when the data can be sent as a percentage of the total batch creation time. To change the length of this time interval, you must change the value of this registry key on each managed computer.

For example, the data is sent to the CMDB every seven days (168 hours) and the Fuzzy Factor value is 10. Then the length of the interval is 10% of seven days or about 17 hours. Half of this interval precedes the specified send time and half of it follows. Thus the time interval in which the data is sent would start after about 159 hours and end after 177 hours.

Application metering records data for each metered application in the order in which it is stored in the data file.

Table: Application summary data

Field

Description

Example

FileResourceGUID

Resource guid that is generated by using various attributes of a file. For example, its internal name, manufacturer, version etc.

{018B191B-47AE-4180-9FCD- 7F3CEA4F1E12}

User Guid

Resource guid that is generated for a specific user on a domain.

{493435F7-3B17-4C4C-B07F- C23E7AB7781F}

Last Start

The date when the application was last started.

11/13/2012 8:38:18 A.M.

Month Year

Month and year of the monitoring period.

September 2012

Run Count

Number of times the application was started during the monitoring period.

3

Denial Count

Number of times the use of the application was denied during the monitoring period.

1

Total Run Time

Total amount of time in seconds that the application was used during the monitoring period

When the application is monitored, this value is updated every 30 seconds.

188714

Peak Memory

Maximum amount of memory in bytes used by the application during the monitoring period. When the application is monitored, this value is updated every 30 seconds.

7921664

Average CPU

Average CPU usage by the application during the monitoring period, where 100 equals 100 percent usage. When the application is monitored, this value is updated every 30 seconds.

0.7652

Month End Summary

Specifies whether the current set of application summary data is the final set for the month.

0 (or false) = not the final data

1 (or true) = the final data

0