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. The default parameters associated with this test are as follows:

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

• In the HOST text box, the host name of the server for which the test is to be configured has to be specified.

• The port number to which the selected server is listening to has to be mentioned in the PORT text box.

• 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*.*.

• To make diagnosis more efficient and accurate, the eG system embeds an optional detailed diagnostic capability. With this capability, the eG agents can be configured to run detailed, more elaborate tests as and when specific problems are detected. To enable the detailed diagnosis capability of this test, by default, for a particular server, choose the On option against DETAILED DIAGNOSIS. To disable the capability, click on the Off option.

  The option to selectively enable/disable the detailed diagnosis capability will be available only if the following conditions are fulfilled:

  • The eG manager license should allow the detailed diagnosis capability

  • Both the bad and normal frequencies configured for the detailed diagnosis measures should not be 0.

• If multiple components of the same component type are awaiting configuration, then an APPLY TO OTHER COMPONENTS check box will appear in this page. Clicking on this check box will allow you to apply the configuration to all/selected components of that type.

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

When changing the configuration for specific servers, a “*” beside the text box corresponding to the parameter signifies that these values have to be manually configured by the user. The parameter values that require to be configured will typically be prefixed with a “$” or contain a series of “*”. A value of "none" in the parameter value indicates that the corresponding parameter value can be changed if required.