|
<< Click to Display Table of Contents >> Navigation: General Functions > Logging > Trimming |
The various logs maintained by the MIE are kept trimmed based on a defined retention period. This is to keep the logs from growing too large and affecting performance.
Trimming is handled by Housekeeping and can be constrained on when it is allowed to run (since trimming can result in the deletion of many records). The time of day when log trimming is allowed to run is governed by the MIE setting TrimLogsWindow, which can only be set by ESI.
Log retention is governed by a hierarchy as follows:
1. Retention override specified by ESI for the given log
If that is blank then,
2. Customer setting DaysToKeepLogRecords.
If that is blank, then,
3. 90 days default.
In the table below (default) means there is no override for the table, in which case the customer setting DaysToKeepLogRecords will be used, or 90 days if the setting is blank.
The IMAC stage archive and offline tables are handled differently, with records from specific catch points having retention periods set by the catch point roles table.
The following logs are automatically trimmed by the MIE: (retention time is in days)
Log |
Purpose |
Retention |
Maintains error information for remote clients (such as RDCm and ASN Processor). |
(default) |
|
Maintains error information for some MIE-encountered errors. |
(default) |
|
Maintains field-by-field change information. |
(default) |
|
Maintains completion information on various unattended jobs. |
30 |
|
Maintains all jobs that are (or have been) queued for operation, along with their current status. |
30 |
|
Maintains data from various catch points, including the ASN processor. Such data is Consolidated periodically into the Asset Management module's primary tables. |
(default) |
|
Asset Management Staging Archive Table |
Once records reach their retention in the staging table, or when a new record for the same catch point and asset is presented, or if a catch point is set to immediately archive after processing, those records are removed from the staging table and archived to this archive table. When performing catch point history research, that history is pulled from a union of this table and the staging table. Note, when this table is trimmed certain records will be moved to the offline table. Those records are defined in the Catch point roles table - mainly certain catch points that have been defined as fulfilling pre-defined roles will have their records moved to the offline table after the retention period expires. All other records will simply be removed. |
(default) Except Autodiscovery role = 90 |
Asset Management Staging Offline table |
Records that pass the retention period as defined in the roles table to which that record's catch point is assigned (if any) are moved from the staging archive table to this staging offline table. As its name suggests, once records are moved to this table, they are no longer visible to the user interface, export, or reporting. Records are held in this table until they reach the retention as defined for this table, after which they are physically deleted. |
365 |
Companion table to the Asset Management module's Staging table. Contains software found on various assets present in the staging table. |
(default) |
|
Deletes |
Keeps track of record deletions made through the user interface |
(default) |
Logins |
Keeps track of all login/logout attempts. |
(default) |
Workflow Threads |
Keeps track of all workflow threads |
180 |
Workflow queue |
Keeps track of all points in all workflow threads where the wofklow stops to wait for a response (process-then-decision) process point. |
180 |