Skip to Content
Information
Unsupported content Version 2.7.41 of the product is in limited support, while versions 2.7.43 and 2.7.44 are fully supported. This documentation includes content for all versions. You will not be able to leave comments for version 2.7.41.

 

Scheduling file monitoring

The KM scans files at each polling cycle (every two minutes by default), continuously. You can define the KM to schedule scans on a weekly basis and multiple schedules for weekdays including adding different schedules for each day. If you want to only scan files for a particular time period each day, you can schedule the KM to scan files starting at a specific time of day for a specified duration. For example, you can configure the KM to start scanning a file every day at 09:00:00 for a duration of three hours. During the specified time, the KM scans the file, ending the scan at 12:00:00. It scans the file every two minutes during the specified time period.

While monitoring the latest log file, when the KM discovers a new log file during a polling cycle, it monitors the earlier log file as well as the new file discovered during that polling cycles.

To schedule a file scan

  1. Access the LOGT application menu for the instance as described in Accessing Menu Commands, InfoBoxes, and Online Help.
  2. Select Advanced Features > Schedule Log Scan.
  3. In the Schedule Log Scan dialog box, enter the time of day that you want to start monitoring in the Start Time of Day text box. (Use a 24-hour clock.)
  4. In the Scheduled Duration text box, enter the length of time that you want the scan to run in hours, minutes, and seconds.
  5. Select one or more of the Sunday, Monday, Tuesday, Wednesday, Thursday, Friday, Saturday, All Weekdays check boxes depending on the day(s) of the week when you want to schedule a log scan. All Weekday s allows you to define a schedule on a daily basis.
  6. (Optional) If you want the KM to go into alarm if the string is not matched during the specified scan time, select the Generate Alert if no Match Found at Scan End check box.
  7. (Optional) If you want to enter the actual end time of the schedule instead of the scheduled duration, select the Consider "Scheduled Duration" as "Scheduled End time" check box. This is global to all schedules.
  8. Click Add to add the defined schedule to List Scheduled Log.
  9. Click Delete to delete a schedule from List Scheduled Log.
  10. Click Update to execute the Add and Delete operations and update the list of scheduled log files.

To hold the scheduled list, use the PMG/CONFIG/label/actSchdlList configuration variable. To set the specified duration to be considered as the End time, use the PMG/CONFIG/label/actDurAsEndTime configuration variable. You must add these variables manually.

If you are modifying an existing LOG application instance that was created using PATROL KM for Log Management 2.4.20 or earlier, you must convert the old format of the scheduled log scanning to the new format. This deletes the PMG/CONFIG/label/actResetCount, PMG/CONFIG/label/actStart, and PMG/CONFIG/label/actDur configuration variables, and creates the PMG/CONFIG/label/actSchdlList and PMG/CONFIG/label/actDurAsEndTime configuration variables.

However, the KM creates only the PMG/CONFIG/label/actSchdlList and PMG/CONFIG/label/actDurAsEndTime variables under the following circumstances:

  • You configure the scheduled log scan for a new LOG application instance with version 2.5.00 or later of the PATROL KM for Log Management.
  • You modify a LOG application instance created using version 2.4.20 or earlier of the product, which does not have a scheduled log scan.

Product Short scans the file every day at the specified time for the specified duration.

 

Tip: For faster searching, add an asterisk to the end of your partial query. Example: cert*

BMC PATROL for Log Management 2.7