Configuration of FileChangeTest

This test reports whether configured files are available or not, and if available, reports the size of the individual files.

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.

• In the HOST text box, specify the IP address of the host for which this test is to be configured.

• Provide a comma-separated list of the full path of the files that are to be monitored. For instance, on a Unix host, your specification can be: opt/usr/alert.log,opt/tmp/error.log. On a Windows host, your specification can be: C:\eGurkha\agent\logs\agentout.log,C:\eGurkha\agent\logs\agenterr.log.

  Also, if you want to monitor files with names that include a date, then your filename specification should indicate the date format used for naming the files. For instance, to monitor all files that are named error, but which end with dates that are of the format DDMMYY, your filename specification should be: C:\logs\errorDDMMYY. As per this specification, files such as error21082015, error22082015, and error24082015 will be monitored.

  Your filename specification can include file names with dates and without dates - for eg., C:\eGurkha\agent\logs\agentout.log,C:\eGurkha\agent\logs\agenterr.log,C:\logs\errorDDMMYY,C:\errorlogs\MMDDYYYY_error

  If you wish to monitor the latest file in a folder that consists of too many files with the same extension, say for example .log, then your FILENAME specification should be : C:\Temp\*.log.

  Note:

  Wildcard characters are not supported while entering the full path of the files in the FILENAME text box. So, provide the exact path of the files in the same.

• Using this test, you can also monitor all files with names that include a date. If your filename specification above includes files with dates, then set the DATE PATTERN flag to Yes. If this is done, then the test will look for date patterns in your filename specification. If your filename specification does not include data patterns, set this flag to No. If this is done, then the test will not look for date patterns in your filename specification. Say that you include a file name that embeds a date pattern in your filename specification - eg., C:\logs\errorMMDDYYYY - and set the date pattern flag to No. In this case, the test will disregard the date pattern MMDDYYYY, and will instead search for a file with the name, errorMMDDYYYY

• If the FILE name parameter is configured with the path of files to be monitored then set this flag to Yes, and if the Filename parameter is configured with the path of directories that contains the files then set this flag to No. By default, this flag is set to No.

• If multiple components of the same component type are awaiting configuration, then an APPLY TO OTHER COMPONENTS button will appear in this page. Clicking on this button 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.