If you choose to truncate a log file, the file does not use a defined bookmark to reference its position within the log file. Therefore, you must indicate how you want the log file monitor to interact with the log file when the file has been truncated.
You might detect a small performance gain in running the log file resource monitor when the log file is truncated. However, you will sacrifice accuracy within your log file data, exposing the data and monitoring operations to an unnecessarily high level of risk and unpredictable accuracy in your log file reads.
You can choose either of the following truncation actions:
Search only new data
OpenEdge Management resets the log file monitor's internal place marker to the end of the file on its first poll after the file has been truncated.
Search entire file
OpenEdge Management searches the log file from beginning to end on its first poll after the file has been truncated. Remember that this technique will ensure that no data is missed when a file is truncated, but much of the file could be searched a second time. If the file is very large, this can be a slow operation.
Search only new data