File System Monitoring

The aim of the File System monitoring tool is to enable operators to rapidly identify impacted applications by distinguishing and specifying what applications rely on which file systems.

File systems (or Windows logical disks) are often a critical resource for applications. Although file systems are already monitored by BMC Performance Manager for Servers, operators often do not know which application is impacted when a file system is full.

To create a new file system monitoring, right-click the Application/Container icon in the PATROL Console and select KM Commands > New > File System monitoring...

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

Select a File System: This drop-list box contains the list of file systems on the computer. Select the file system you wish to monitor.

UNIX/Linux with more than 30 file systems: On UNIX/Linux servers with more than 30 file systems, PSL limitations render the correct functioning of a long drop-down list difficult, hence these systems will display the dialogue box. By clicking Existing File Systems a small box showing current file systems will appear. Again, owing to PSL limitation, selection of the drive/file system with the cursor is not possible – you are required to enter the drive manually. The panel that shows all the drives is for display/information purpose only. Click Accept/Cancel.

•	FreeMegabytes: Free space left in megabytes. It is possible to trigger an alert when the free space in MB is lower than a given value.

•	FreeSpacePercent: Displays the free space in percentage. You can configure Monitoring Studio to trigger an alert when the percentage of free space on the file system is lower than a given threshold.

•	UsedSpaceGrowthPercentage: Shows how fast the file system is filled up, in percentage of its size (in percentage per hour - %/hour). Note that the UsedSpaceGrowthPercent parameter may have negative values.

•	UsedSpaceGrowthSpeed: Shows how fast the file system is filled-up (in megabytes per hour – MB/hour). Note that the UsedSpaceGrowthSpeed parameter may have negative values.

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