PATROL for Log Management: LOG KM is not working properly for the latest file in Dynamic file monitoring

Knowledge Article

Article Number

000288107

Old Article Number

000079437

Article Type

Solutions to a Product Problem

Title

PATROL for Log Management: LOG KM is not working properly for the latest file in Dynamic file monitoring

Summary

LOG KM is not working properly for the latest file in Dynamic file monitoring

Product

PATROL for Log Management

Component

PATROL for Log Management

Applies to

All supported version of PATROL for Log Management

Problem

LOG KM not working properly for the latest file in Dynamic file monitoring

When the LOG KM is configured to monitor multiple files (eg., files*.log) to search for a specific string the KM finds a new file (eg., files2.log) with the required string in it but the KM indicates "0" (zero) for the "LOGSearchString" parameter and it does not alert.

Cause

Solution

It's a core behavior of the LOG KM.

For monitoring the latest file and reading the first attempt all is needed is to declare the following parameter in the configuration.

1./PMG/CONFIG/_INSTANCE_NAME_/actInitialReadEOF = 2

The above parameter will allow the first read to not be missed. This parameter indicates to the LOG KM to read the file from the beginning.

When the parameter actFileBegin=1 (Read from the beginning),
Then the file will be read from the beginning each time (If it was modified - Means redundant alert about the same match)
While on the other hand while it's disabled and the actInitialReadEOF equals to 2 it will be read only the first time and after that only the added text will be checked for a match.

For further configuration queries please look into the documentation link below:
https://docs.bmc.com/docs/display/public/logmanagement27/PATROL+KM+for+Log+Management+configuration+variables

Attachment(s):

Manage Support IDs

BMC Contact Options

Knowledge Article