Objective

Prerequisites 

• Access to EventLog Analyzer
• Administrative role or Manage Log Import role to create log import schedule on the EventLog Analyzer instance
• Knowledge of the log source and the file names that you need to import.
• Access to the location where the files are stored.

Steps to follow

1. Login to EventLog Analyzer user interface.
2. Navigate to Settings >> Log Source Configuration >> Import Logs
3. Select the type of import as Remote or S3 Bucket. Refer How to import logs from Remote path or How to import logs from S3 bucket
   NOTE: Scheduled log import is not available for local path.
4. Post selecting the files and associated device, Enable check box for Schedule Log import.
5. Update the Schedule time interval using any of the condition as follows:
• Hourly - Scheduled imports occur every hour at a specified minute mark. The minute value can range from 0 to 55 and can be set in multiples of 5.
• Daily - Scheduled imports occur daily at a specified hour and minute. The hour value can range from 0 to 23, and the minute value can range from 0 to 55 in multiples of 5. The time is specified in 24-hour format.
• Weekly - Scheduled imports occur weekly on a specified day, hour, and minute. Days are represented from Sunday to Saturday. The hour value can range from 0 to 23, and the minute value can range from 0 to 55 in multiples of 5. Time is specified in 24-hour format.
• Monthly - Scheduled imports occur monthly on the specified date, hour, and minute. The date can range from 1 to 30, hour value can range from 0 to 23, and the minute value can range from 0 to 55 in multiples of 5. Time is specified in 24-hour format.
• Every - Scheduled imports occur at the specified minute interval. The minimum value is 1, and it must be a whole number (no decimal values).
  Note: From the above screenshot, the schedule import is configured to import the logs daily at 10:30 AM (EventLog Analyzer server time)
6. If the logs are written in a specifc log file the above configuration can be performed to collect the logs. If the application creates new log files with unique filenames based on date/file size/timestamp etc, you can enable Specify filename pattern to import them.
7. Specifying the File name pattern allows the EventLog Analyzer to understand what will be the name of the file that will be created. Once a new file is created, EventLog Analyzer will understand the pattern of the new file name and will import them automatically.
8. Define the Naming Convention:
• Choose Advanced Options to create a name and pattern.
• Enter the static values manually and dynamic values using any of the following pattern from the drop down available.
• Day
• Month
• Year
• Weekday
• Week in year
• Week in month
• Hour
• Minute
• Second
• Number Increments

• Include the date and time in a consistent format (e.g., YYYYMMDD_HHMMSS).
• Add the static string values as per file name

• 2023 – Year, represented as a 4-digit string (YYYY)

• 10 – Month, represented as a 2-digit string (MM)

• 05 – Date, represented as a 2-digit string (DD)

• _ – Static string value

• 14 – Hour, represented as a 2-digit string (HH)

• 30 – Minute, represented as a 2-digit string (MM)

• 00 – Second, represented as a 2-digit string (SS)

• _MSSQL_ERROR_PROD – Static string value

9. Once you create the pattern, Choose Apply to save the pattern.
10. Choose import to initiate the import.

 Validation and confirmation

• Verify that the naming convention is applied correctly by reviewing the imported log filenames under Advanced Options.
• Check if the logs are imported in Search and check the import status in Import Logs settings tab.

 Tips

• Configure log sources to generate multiple files using an incremental naming convention instead of writing all logs to a single file. This helps prevent large file sizes and improves manageability.
• EventLog Analyzer can resume reading from the exact line where the last scheduled import ended. If multiple new files are created, the application continues log collection by reading to the end of the current file and then automatically switches to the next file based on the defined file name pattern.
• Imported logs are parsed using the timestamps recorded in the log entries themselves.
• Using a consistent naming convention simplifies both log management and analysis.

Related topics and articles