This test reports the file information such as the size of the file and the last time the file was modified. In Linux environments, the file information will include the name of the group to which the user accessing the file belongs to and the permissions granted to the user to access the file.

The default parameters associated with this test are:

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

• Specify the host for which the test is to be configured in the HOST text box.

• Specify the port at which the specified HOST listens in the PORT text box. By default, this is NULL.

• In the FILENAME text box, specify the full path to the directory or file to be monitored. For e.g., c:\app\logdir. Multiple directories or files can be configured in the following format: <DisplayName1>@<DirectoryPath1>,<DisplayName2>@<DirectoryPath2>,... This implies that 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 a directory has been specified in the FILENAME text box and the INCLUDEFILESINDIR flag is set to Yes, then all the files and subdirectories of the specified directory will be tracked for information. By default, this flag is set to No.

• If you wish to include the subdirectories of the directory specified in the FILENAME text box in the scope of monitoring, then specify the value true in the INCLUDESUBDIRECTORIES text box. If multiple directories have been configured in the FILENAME text box, then, the INCLUDESUBDIRECTORIES text box allows you the flexibility to enable sub-directory monitoring for a few of the configured directories and to disable the same for a few others. For instance, if the subdirectories of the directory DisplayName1 needs to be monitored and the subdirectories of the directory DisplayName2 need not be monitored, then the INCLUDESUBDIRECTORIES text box has to be populated as follows: <DisplayName1>@true,<DisplayName2@false.

• If you wish to exclude certain files from the scope of monitoring, then specify them in the EXCLUDEPATTERN text box. If no file needs to be excluded from monitoring, set the value of the EXCLUDEPATTERN text box to none. If multiple directories have been specified in the FILENAME text box, and a few files need to be excluded from monitoring for some of these directories, then configure a set of exclude patterns for each such directory; this specification should be in the following format: <DisplayName1>@*Pattern1*:*Pattern2*,<DisplayName2>@*Pattern3*:*Pattern4*. Say for example, you wish to exclude the files - error and warning from the directories LogPath and OraPath mentioned in the FILENAME text box. In this case, your EXCLUDEPATTERN text box specification can be: LogPath@*error*:*warning*, OraPath@*error*:*warning*. If, in addition to directories, one/more files have also been configured for monitoring in the FILENAME text box, then your EXCLUDEPATTERN specification can ignore the files. However, if your FILENAME specification consists of files alone, then, you can specify none in the EXCLUDEPATTERN text box.

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