Folder Monitoring

The aim of the tool is to monitor folders (directories) that store files processed by the application: measure their size, growth and flow (including how many files move in, how many out, etc.).

Folders/directories are often critical elements for an application and checking their content is a good way to monitor the application's health.

•	Monitoring Studio tests and measures the content of this folder every two minutes (total size, number of files) and compute the file flows (how many new files, how many removed files) etc depending on the options selected.

•	Ensure that your application is not overloaded (number of files to be processed, e.g.)

•	Measure the application activity (how many removed files, that is, how many have been processed)

•	Check the age of the newest file (whether the data is coming in properly…)

•	Check the age of the oldest file (whether the application late in processing queued files).

Folder monitoring may be time-consuming for large size folders. Therefore, Monitoring Studio will automatically reduce its monitoring features when the monitored folder contains more than 1000 files. If you want to avoid the use of this limit, you can set the configuration variable "/MASAI/SENTRY8/folderLimit" to a value greater than 1000.

To create a new folder monitoring, right-click the application/container icon in the PATROL Console and select KM Commands > New > Folder monitoring...

To edit an existing folder monitoring, right-click the folder icon in the PATROL Console and select KM Commands > Edit.

Folder name and path: Enter the name and path of the folder (directory) to be monitored.

Include sub-folders: Check this box to monitor all the sub-folders of the above-specified folder.

Monitor only files matching the mask below (optional): Specify the file types or enter masks, and only these files will be monitored.

You can use wildcards such as "*" to replace any number of characters, or "?" to replace just one character. You may also use several masks separated by ";". Monitoring Studio will only take into account the files matching the masks entered.

Example

You can enter:.txt;myFiles?.log;file.*, and all files matching these masks will be monitored

▪	FolderSize: Total size of all files in the folder (and sub-folders if asked).

▪	GrowthPercentage: Growth of the folder since the last polling. This is the last recorded size divided by the polling interval. Unit: percent per minute. This parameter can also be negative.

▪	GrowthSpeed: Growth speed of the folder since the last polling, divided by the polling interval. Unit: kilobytes per minute.

▪	DeletedFileCount: Number of files deleted from this folder since the last polling, divided by the polling interval. Unit: files per minute

▪	NewFileCount: Number of new files added to this folder since the last polling, divided by the polling interval. Unit: files per minute

▪	ModifiedFileCount: Number of files modified since the last polling, divided by the polling interval. Unit: files per minute

▪	LastModifiedFileElapsedTime: Time elapsed since the last modification/creation of a file in this folder. Unit: minutes

▪	OldestModifiedFileElapsedTime: Time lapsed since the last modification/creation of the oldest file in this folder. Unit: minutes

Object internal identifier (ID): PATROL internal identifier of this monitored object.

What thresholds do you want to set for the newly created instance? A drop-down list allows you to select the mode of setting alert thresholds:

•	Use default thresholds: Uses the default thresholds set by Monitoring Studio

•	Set custom thresholds: Allows you to customize the thresholds for all parameters of the instance

•

Use default thresholds and customize them: Sets the default Monitoring Studio thresholds on certain parameters (see list of parameters with default thresholds) and then allows you to customize any/all of them. This is mainly intended to help save time if you wish to customize the thresholds of just one of many parameters for the instance, and leave the default settings for the others.

If you select Use default thresholds and customize them; on clicking Finish, the Set Thresholds panel will appear, certain parameters for the instance may appear with an asterisk symbol - indicating that they already have thresholds. You can then customize (any/all) the thresholds of the parameters as per your specific needs.

•	Do not set any thresholds for now: No thresholds will be set on any parameter of the instance, and as a result no alerts will be triggered. Monitoring Studio will poll the object and return the output of the polling – but will not raise any alerts until you set thresholds.

Thresholds can be set or modified at anytime by right-clicking on the instance > KM commands > Set Thresholds.