Aggregation and archiving activity: archive, send, purge, and so on. This topic describes the domain's entities and attributes.
Available to roles: admin
Activity Types Entity
Available only from the Aggregation/Archive domain, which by default is available to users assigned the admin role only. The Activity Types entity can be accessed only from the owning Aggregation/Import/Export Log Entity. It identifies a type of action (Prepare for Aggregation, Encrypt, Send, etc.).
|Activity Type||Description of an aggregation/import/export activity.|
Agg/Archive Log Entity
Available only from the Aggregation/Archive domain, which by default is available to users assigned the admin role only. One or more Aggregation/Import/Export Log entities are created for each activity. For example, when an aggregator system imports data, you typically see at least four activities:Prepare for Aggregation, Check Duplicate Import (one per file exported to this aggregator), Extract (one per file to be merged), Merge (one per file merged)
|Comment||Additional comment for the activity.|
|End Time||Ending time of activity.|
Name of file used for the activity. Files created by the archive and export operations are named as follows:
The date of the data contained on the file, in yyyy-mm-dd format is data_date, near the end of the file name (just before .dbdump.enc). Take care that you do not confuse this date with the run date, which appears earlier in the file name, and is the date that the data was archived or exported.
|Guardium Host Name||The name of the Guardium host.|
The UTC offset. This is done in particular for aggregators that have collectors in different time zones and so that activities that happened hours apart do not seem as if they happened at the same time when imported to the aggregator.
For instance, on an aggregator that aggregates data from different time zones, you can see session start of one record that is 21:00 with original timezone UTC-02:00 and another record where session start is 21:00 with original timezone UTC-05:00, This means that these events occurred 3 hours apart, but at the same respective local time (9 PM).
|Period End||Ending time for the activity being acted upon.|
|Period Start||Starting time for the data being acted upon. Each archiving or aggregation activity operates on one full day of activity.|
|Records Purged||If the activity type is Purge, the number of records purged. Otherwise, N/A.|
|Status||Status of the aggregation/import/export log activity.|
|Start Time||Starting time of activity.|
|Timestamp||Updated at the start and end of the activity being logged (prepare for archiving, encrypt, send, etc.).|
|User Name||User name under which activity initiated.|
Agg/Archive Debug Log Entity
|Aggregation Date||Date for the data being acted upon. Each archiving or aggregation activity operates on one full day of activity.|
|Aggregation Duration||Duration of the activity described by Aggregation Stage.|
|Aggregation Exception||If there was any exception during the activity it is presented in this field.|
|Aggregation Stage||Stage of the aggregation activity, for example, "Initialization", "Post Purge - START"|
|Aggregation Status||Status of the Stage, for example, D: done, I: info, W: warning, E: exception|
|Aggregation Table Name||The name of the table, on which the activity is done.|
|Details||Additional info, for example, "Max age is -1, age is 60. 0 days had been found"|
Aggregation process name. For example:
|Records Deleted||The number of records deleted from the table described in "Aggregation Table Name" in this Aggregation Stage|
|Records Inserted||The number of records inserted to the table described in "Aggregation Table Name" in this Aggregation Stage|
|Records Updated||The number of records updated in the table described in "Aggregation Table Name" in this Aggregation Stage|
|Run Log Id||Used Internally.|
|Timestamp||Time when the record was inserted in the Agg/Archive Log|