Disk Space Test

How often should the test be executed.

The host for which the test is to be configured.

Set this flag to Yes, if you want the test to automatically discover NFS drives on your system and report their status as well. By default, this flag is set to No.

This parameter is only applicable for Linux systems.

By default, this flag is set to No indicating that this test will monitor all file systems including temporary, dynamic or automatically mounted file systems and report metrics. However, you can filter the persistent and configured file systems that are explicitly defined in the system’s /etc/fstab file by setting this flag to Yes.

This parameter is applicable only for AIX, Solaris and HPUX components.

By default, this flag is set to No indicating that this test will not report the local NFS (Network File System) name used by the target host while presenting NFS shares to NFS servers and clients. However, if you set this flag to Yes, the test will include the local NFS name as descriptors. This allows you to view how the host identifies and exposes its NFS resources during sharing or mounting operations.

Specify the comma-separated list of folders that this test should ignore when checking availability before reporting the metrics. By default, this parameter is set to *users*,*appstream*. However, you can modify this list if required.

Optionally, you can configure this test to automatically initiate a disk cleanup action, if any disk partition on the target host is found to be running out of free disk space. This way, you can enable the test to pre-empt a potential space crunch and ensure the peak performance and uninterrupted functioning of applications running on the target host. To enable the test to take such corrective action automatically, set this flag to Yes (default: No).

This parameter applies only if the 'Automated Action Enabled' flag is set to 'Yes'.

By default, this parameter is set to 95%. This means that, by default, this test will automatically cleanup unwanted files (eg., temp files) on any disk for which the Percent usage measure reports the value 95% or higher. This way, the test makes sure that there is always adequate free space on disks for the use of virtual applications. If you want, you can change the value of this parameter to suit the needs of your environment.

Against this parameter, you can provide a comma-separated list of disk partitions that you want to exclude from monitoring. For example, on Unix systems, you can use this parameter to exclude temporary partitions that the Unix system itself creates from monitoring.

These parameters are applicable to Windows systems only. When monitoring a Windows system, if the DISCOVER NFS flag of this test is set to Yes, then the test should be configured with the privileges of a valid domain user in order to auto-discover NFS drives and report their usage and status. In such a case therefore, specify a valid Windows domain name against DOMAIN , provide the name of a valid user in that domain against DOMAIN USER, and specify the password of that user against PASSWORD. Once the domain user credentials are provided, the test auto-discovers all those NFS drives on the target Windows system to which the configured domain user has access.

Retype the PASSWORD of the configured domain user here.

Specify the maximum duration (in seconds) for which the test will wait for a response from the server. The default timeout period is 30 seconds.

This parameter applies only to Linux and Solaris systems. By default, the USE SUDO parameter is set to No. This indicates that, by default, this test will report metrics by executing the df -Pk –l command on the Solaris host. However, in some highly secure environments, the eG agent install user may not have the permissions to execute this command directly. In such cases, do the following:

• Edit the sudoers file on the target host and append an entry of the following format to it:

  <eG_agent_install_user> ALL=(ALL) NOPASSWD:<Command>

  For instance, if the eG agent install user is eguser, then the entry in the sudoers file should be:

  eguser ALL=(ALL) NOPASSWD: df –Pk -l

Finally, save the file.

Then, when configuring the test using the eG admin interface, set the use sudo parameter to Yes. This will enable the eG agent to execute the sudo df –Pk –l command and retrieve the desired metrics.

This parameter is relevant only when the use sudo parameter is set to ‘Yes’. By default, the sudo path is set to none. This implies that the sudo command is in its default location – i.e., in the  /usr/bin or /usr/sbin folder of the target Solaris host. In this case, the eG agent automatically runs the metastat command with sudo from its default location, once the use sudo flag is set to Yes. However, if the sudo command is available in a different location in your environment, you will have to explicitly specify the full path to the sudo command in the sudo path text box to enable the eG agent to run the sudo command. 

This flag is applicable only when the target Linux host is monitored in the agentless manner. In highly secure environments, eG Enterprise could not perform agentless monitoring on a Linux host using SSH. To enable monitoring of the Linux hosts in such environments, set the HIGH SECURITY flag to Yes. It indicates that eG Enterprise will connect to the target Linux host in a more secure way and collect performance metrics. By default, this flag is set to No.

This parameter is applicable only for the Windows component.

By default, this parameter is set to 90%. This means that, by default, this test will report the detailed diagnosis for the Percent usage measure only when the value reported for the measure is 90% and above. However, you can override this setting as per your requirement.

This parameter applies to Windows systems only.

Specify the number of directory levels that this test should consider while monitoring folders on the disk. By default, this parameter is set to 3. However, you can override this setting if required.

Refers to the frequency with which detailed diagnosis measures are to be generated for this test. The default is 1:1. This indicates that, by default, detailed measures will be generated every time this test runs, and also every time the test detects a problem. You can modify this frequency, if you so desire. Also, if you intend to disable the detailed diagnosis capability for this test, you can do so by specifying none against DD frequency.