You are here: Application Interface > Main window > Organization tree > Tracking files import history

Tracking file import history

This dialog box shows the detail of data imported from messages tracking files for a given server.

Use the Delete button or the Del key to remove a selected import  from the database.

This window can be reached through the Server Properties dialog box.

Column header Description
File name Message tracking file name.
File date Message tracking file date.
File size (KB) Message tracking file size, in KiloBytes.
Processed Number of usable events found in the message tracking file.
Recorded Number of events recorded into the database.
Ratio Percentage of recorded events vs. number of usable events.
Duration Import task duration.
Console Name of the console (workstation) that carried out the import task.
ImportDate Import task date.
Status This status may be:
  • completed-noError: The message tracking file was correctly imported.
  • Partial-noError: The message tracking file was partially imported because it was not completed at the time of import. Import will be completed at next import.

Note: Message tracking files are closed at midnight UTC/GMT, wherever you are located. If you decide to import today's message tracking file, it will probably not be complete. The import process will record the number of processed lines and mark the file as partially imported. Only new lines will be processed during the next import until it is completed.

  • noEvents-LogNotFound: No event has been imported imported because no message tracking file was found for the specified date.
  • noEvents-Aborted: The message tracking file was not imported because the import task was cancelled.
  • Damaged: The message tracking file was found to be damaged and could not be imported.
Type of imported data

Values in these columns can be:

  • X: import requested.
  • - : import not requested.
  • <empty>: no matching data was found in the message tracking file.

For more information about imported event types, see Data source: Message tracking and Message Tracking tab.
of