Application metering data is stored on metered computers and then sent to the CMDB. Over time, you may want to delete (purge) application metering data. You can purge metering events, reports, and summary data. You can also configure the settings that purge the data at configured time intervals.
See“Application summary data”on page 139. This task is a step in the following processes:
■ Tracking usage of the managed software products ■ Metering and denying applications
See“Tracking usage of the managed software products in the enhanced Symantec Management Console Software view”on page 109.
See“Metering applications”on page 123.
To configure the purging settings for application metering data
1
In the Symantec Management Console, on the Settings menu, click AllSettings.
2
In the left pane, under Settings, expand Discovery and Inventory > InventorySolution, and then click Application Metering Configuration.
3
To purge events, check the Purge events older than ... days box, type the number of days, and then click Purge Events Now.4
To purge reports, check the Purge reports older than ... days box, type the number of days, and then click Purge Reports Now.5
To purge summary data, in the Purge when older than ... months textbox, type the number of months, and then click Purge Data Now.6
To purge archives with summary data, check Purge archives older than ...months box, type the number of months, and then click Purge Archive Data Now.
7
Click Save changes.Application summary data
(Windows only)139 Software-based usage tracking, metering, and denying applications
Each time a metered application starts, the 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 in an enabled application metering policy.
You can view this data in the Executable Usage report. See“Viewing inventory data in reports”on page 168.
To prevent an overload to the system when this data is sent, the data is not all sent at the same time. The data is randomly sent over an interval of time. A value in theHKEY_LOCAL_MACHINE\SOFTWARE\Altiris\Application Metering registry keyon each client computer determines the length of the interval. The name of
the value is Fuzzy Factor, and its default value is 10. 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 client computer. Any registry changes should be done with caution.
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.
See“Configuring the purging settings for application metering data”on page 139. Table 8-7 Application summary data
Example Description
Field
{018B191B-47AE-4180-9FCD- 7F3CEA4F1E12}
Resource guid that is generated by using various attributes of a file. For example, its internal name, manufacturer, version etc. FileResourceGUID
Software-based usage tracking, metering, and denying applications
Application summary data
Table 8-7 Application summary data (continued) Example Description Field {493435F7-3B17-4C4C-B07F- C23E7AB7781F}
Resource guid that is generated for a specific user on a domain. User Guid
11/13/2012 8:38:18 A.M. Date the application was last
started Last Start
September 2012 Month and year of the monitoring
period Month Year
3 Number of times the application was started during the monitoring period.
Run Count
1 Number of times the use of the application was denied during the monitoring period.
Denial Count
188714 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.
Total Run Time
7921664 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.
Peak Memory
0.7652 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. Average CPU
0 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 Month End
Summary
141 Software-based usage tracking, metering, and denying applications
Software-based usage tracking, metering, and denying applications
Application summary data