|
The Imported Log Files link lets you import a windows event log file (type .evt format) from the local machine or remotely, through FTP. You can import both Event Log and Application Log files.
Importing Event Log and Application Log files are explained below.
![]() |
If you importing an event log file which is much older than the configured DB Storage option, then such imported event log files are automatically considered as Throw Away Reports. |
| Some Applications create log file with new name (with time stamp appended) everyday. If the Application log files are to be imported, you do not have to change the filename daily, instead select the Change filename dynamically option while importing the logs. Selecting the option displays the the Filename pattern: text box to enter the time stamp pattern that the Proxy server appends when the Proxy server creates the log file daily. A help tip icon displays, (when you hover the mouse on the icon) the mapping of the Timestamp in Filename to the Pattern to be given. Enter the pattern as required. |
The Imported Log Files listing page shows you the list of windows event log files imported, along with details such as the following for each imported event log file.
| Column Head | Description |
|---|---|
| FileName | Name of the imported event log file. Click on the icon to know the details of errors while importing the event log files. |
| HostName | Host which generated the event logs. |
|
LogType |
The event log type can be Application, Security, System, Directory Service, DNS Server, or File Replication Service. |
| ImportType | Whether the event log file has been imported from the local machine or remotely (remote machine name or ip) through FTP. |
| ImportedTime | Timestamp at which the event log file was imported. |
| LogRecord StartTime | Time stamp of the first collected log record in the imported event log file. |
| LogRecord EndTime | Time stamp of the last collected log record in the imported event log file. |
| Report Type | The type of custom report that will be generated. The report type can be Active or Throw Away. |
| Action | Click on the Load & Search link to load the event log file into the inbuilt MySQL DB. |
Click on the Search link to search through the DB for matching criterias. The search criteria can be Source, Severity, Message, Event ID, Type (or Facility). |
|
Click on the DropDB link to drop the imported log file table. |
The Application Log Imports tab of the Imported Log Files listing page shows you the list of application log files imported, along with details such as the following for each imported application log file.
| Column Head | Description |
|---|---|
| File Name | Name of the imported application log file. Click on the icon to know the details of errors while importing the application log files. |
| Format Description | The log format is indicated here. |
| Remote Host | Remote Host from where the application log file has been imported. |
Status |
Indicates the status of file import. Various status are listed below. |
| Imported Time | The time stamp at which the application log file was imported. |
| Size | The size of the imported application log file. |
| Time Taken | The time taken to import the application log file. |
| Action | Click on the Load & Search link to load the event log file into the inbuilt MySQL DB. |
Click on the Search link to search through the DB for matching criterias. The search criteria can be Source, Severity, Message, Event ID, Type (or Facility). |
|
Click on the DropDB link to drop the imported log file table. |
![]() |
All Imported Log Files will automatically get listed on the Archived Files page. |
|