The FileMonitorTest monitors a configured directory, and reports the total number of files in that directory that match configured patterns. In addition, the test also reports the age of the oldest file of all the matching files.

This page depicts the default parameters that need to be configured for the FileMonitorTest.

• The TEST PERIOD list box helps the user to decide how often this test needs to be executed.

• In the FILE PATH text box, specify the full path to the directory to be monitored. For eg., c:\app\logdir. Multiple directory paths can be configured in the following format: <DisplayName1>@<DirectoryPath1>,<DisplayName2>@<DirectoryPath2>,... Every DisplayName will appear as a descriptor of this test. For instance, on a Windows host your specification can be: LogPath:C:\eGurkha\agent\logs,OraPath:C:\Oracle\alerts\logs. Likewise, on a Unix host, your specification can be: LogPath:opt/eGurkha/agent/logs,ErrorPath:opt/usr/tmp/errors.

• If only a single directory has been configured against FILE PATH, then, in this text box, provide a comma-separated list of filename patterns to be monitored. For example, error.log,warning.log. Your pattern specifications can also include wildcard characters. For example, to monitor files with names that begin with the word ‘log’, and those that end with the word ‘err’, your pattern specification can be: log*,*err. Similarly, to monitor those files with names that embed say, ‘warn’, your specification can be: *warn*. A leading * signifies any number of leading characters, and a trailing * signifies any number of trailing characters.

  If multiple directories have been configured against FILE PATH, then, you can specify a file pattern for each directory so configured. Your specification in this case should be of the following format: <DisplayName_of_Filepath1>@<Filename_pattern1>,<DisplayName_of_Filepath2>@<Filename_pattern2>,... For instance, if the FILE PATH has been configured with two directories with display names LogPath and OraPath, the FILENAME PATTERN can be: LogPath:*.log,OraPath:*alert*.*. You can also configure multiple patterns for each directory specified against FILE PATH. For example, if the FILE PATH has been configured with two directories with display names LogPath and OraPath, and you want to monitor all files with the extensions .txt and .log in both these directories, your specification would be: LogPath@*.txt,LogPath@*.log,OraPath@*txt,OraPath@*.log.

• In some environments, file names may begin with the dates on which the files were created/modified. If you want this test to monitor only those files that begin with configured date patterns, then set the DATE PATTERN flag to true. In this case, only those FILENAME PATTERNs that begin with a date pattern will be considered for monitoring by this test. All other patterns will be ignored. If the DATE PATTERN is set to false, then all configured FILENAME PATTERNs will be monitored.

  Say, you want to monitor only those files with names that begin with dates of the format, ddmmyy. To achieve this, first set the DATE PATTERN flag to true, and then, specify the following in your FILENAME PATTERN text box: <DisplayName_of_FilePath>@ddmmyy*.*.

• Once the necessary values have been provided, clicking on the UPDATE button will register the changes made.

When changing default configurations of tests, the values with "$" indicate variables that will be replaced by the eG system according to the specific server being managed - for instance, $hostName is the host/nickname of the target host, $port is the port number of the server being monitored. E.g., for a server xyz:80, $hostName will be changed automatically by the eG manager to "xyz" and $port will be changed to "80" when configuring a test.