How does data aggregation work in NetIQ AppManager? (NETIQKB2862)

How does data aggregation work in NetIQ AppManager?

To move data from the ArchiveData table to the aggregate tables:

1. Go to File | Preferences.
2. Select the Repository tab.
3. Click Data.

   1. Default Period To Keep Points In Data Table:
      Specifies a time period, in days, to make data points in a data stream available for reporting and display in the Graph pane of the Operator Console and in the Chart Console. At the next Time interval to purge old points in repository, if the age of the data point exceeds the time period you set, the data point is deleted from the Data table of the AppManager repository and is no longer available for reporting or display in a graph or chart.
   2. Move Archive Points To Aggregate Table:
      You need to set this because if you do not then the information remains in the Archive data table indefinitely. You need to enter how frequently you want the data moved and purged using the Move Points After option. This option will move the Archive Data to the aggregate table and then delete.
   3. Time Interval To Purge Old Points In Repository:
      Works with Default period to keep points. You specify the time interval, in hours, to truncate data streams in the Data table of the AppManager repository. Any data points that are older than the specified threshold for Default period to keep points in data table are deleted.
   4. Remove Associated Data:
      Is a very good option to have checked for various reasons.  Cleans out all associated data when the job is deleted. Such as graph data, and including policy-based jobs.

4. Click OK.
5. Click Event.

   1. Move Aged Events To Archive Tables In Repository When:
      Select one of the following options to set the schedule for archiving and purging of event data in the repository:
      1. Event Is Closed:
         This option moves events to the archive tables in the repository when the events are closed.
      2. Event Stays Open Status For n Days/Hours:
         This option moves open events to the archive tables in the repository after the specified number of Days/Hours.
      3. Event Stays Closed Status For n Days/Hours:
         This option moves closed events to the archive tables in the repository after the specified number of Days/Hours.
      4. Closed Event Severity Is Greater Than n Severity:
         This option moves closed events to the archive tables in the repository when the event severity is greater than the specified level.
      5. Purge Archived Events In Repository When:
         Select one of the following options to set the schedule for removing archived events from the repository.
      6. Event Has Been Kept For n Days:
         This option purges events that  have been kept in the repository for the specified number of days. Oldest events exceed number of records: This option purges events that exceed the maximum number specified to be kept in the repository.
   2. Remove Associated Events When Jobs Are Deleted:
      Select this to automatically delete all events associated with a deleted job, including policy-based jobs.

Formerly known as NETIQKB2862

The purpose of moving data from the ArchiveData table to the aggregate tables is to provide the functionality to create custom reporting on historical data. This also allows data to be removed from the ArchiveData table.

The data from the ArchiveData table that is sent to the aggregate tables is kept in the aggregate tables indefinitely. This data will eventually need to be manually purged using the utilities provided by SQL Server (for example, Delete and Truncate).

The aggregate tables consist of the following tables:

For Data:ArcAvgDailyData ArcAvgDailyDataHeader ArcAvgHourlyData ArcAvgHourlyDataHeader ArcAvgMonthlyData ArcAvgMonthlyDataHeader

For Events:ArchiveEvent ArchiveEventDetail

 

NOTE: Also see blog "Everything you ever wanted to know about Data" on community.neiq.com in the "AppManager User Group"