[Deprecated] Logical Disk Free Space

Microsoft.Windows.Server.10.0.LogicalDisk.FreeSpace (UnitMonitor)

Monitors the percentage free space and number of free MBytes remaining on a logical disk. Only when both the low percentage free space and low number of free MBytes thresholds are reached, the disk is flagged as having low disk free space.

Knowledge Base article:

Summary

The amount of free disk space on the logical disk volume has fallen below threshold. System performance may be adversely affected and the ability to add or modify existing files on the logical disk volume may not be possible until additional free space is made available.

Configuration

The Logical Disk Free Space monitoring routine is a high configurable solution that enables Operators to set varying threshold values for system and non-system logical disk volumes. In addition separate threshold values can be set for Warning and Error states.

Since logical disk volumes may vary in size from a few gigabytes to many terabytes or more the Logical Disk Free Space monitoring routine requires that an Operator indicate both the Megabyte and Percentage based threshold values that must be passed before the Warning and Error thresholds reached. This means that in order for the threshold to be reached both the Megabyte and Percentage based threshold values for the System or Non-System Drive must be breached.

The default threshold values for the Logical Disk Free Space monitoring routine include:

System Drive Free Space Thresholds (Defaults)

Parameter	Default Value
System Drive Error Mbytes Threshold	100
System Drive Error Percent Threshold	5
System Drive Warning Mbytes Threshold	200
System Drive Warning Percent Threshold	10

Non-System Drive Free Space Thresholds (Defaults)

Parameter	Default Value
Non-System Drive Error Mbytes Threshold	1000
Non-System Drive Error Percent Threshold	5
Non-System Drive Warning Mbytes Threshold	2000
Non-System Drive Warning Percent Threshold	10

Please note that Overrides can be used to change any of the threshold values that are defined above. In addition these thresholds can be applied to all logical disk volume instances in the management group or if needed separate threshold values can be defined for specific logical disk volume instances.

Causes

When existing files grow in size and the new files are added, the free space is taken up on a logical disk. When the amount of free space on the logical disk falls below the threshold, the state for the logical disk will change.

Resolutions

To increase the amount of available disk space, do one or more of the following:

Run Disk Cleanup to gain more free space on the disk.
Back up and remove files, or delete unnecessary files from the disk.
Move files to another disk or to offline storage.
Purchase additional storage or switch to a larger disk.

To view recent disk space history you can use the following view:

Start Disk Capacity View

Element properties:

Target

Microsoft.Windows.Server.10.0.LogicalDisk

Parent Monitor

System.Health.AvailabilityState

Category

Custom

Enabled

False

Alert Generate

True

Alert Severity

MatchMonitorHealth

Alert Priority

Normal

Alert Auto Resolve

True

Monitor Type

Microsoft.Windows.Server.10.0.FreeSpace.Monitortype

Remotable

True

Accessibility

Public

Alert Message

Logical Disk Free Space is running low

The disk {0} on computer {1} is running out of disk space.

RunAs

Default

Source Code:

<UnitMonitor ID="Microsoft.Windows.Server.10.0.LogicalDisk.FreeSpace" Accessibility="Public" Enabled="false" Target="ServervNext!Microsoft.Windows.Server.10.0.LogicalDisk" ParentMonitorID="SystemHealth!System.Health.AvailabilityState" Remotable="true" Priority="Normal" TypeID="Microsoft.Windows.Server.10.0.FreeSpace.Monitortype" ConfirmDelivery="true">

  <Category>Custom</Category>

  <AlertSettings AlertMessage="Microsoft.Windows.Server.10.0.LogicalDisk.FreeSpace.AlertMessage">

    <AlertOnState>Warning</AlertOnState>

    <AutoResolve>true</AutoResolve>

    <AlertPriority>Normal</AlertPriority>

    <AlertSeverity>MatchMonitorHealth</AlertSeverity>

    <AlertParameters>

      <AlertParameter1>$Target/Property[Type="Windows!Microsoft.Windows.LogicalDevice"]/DeviceID$</AlertParameter1>

      <AlertParameter2>$Target/Host/Property[Type="Windows!Microsoft.Windows.Computer"]/PrincipalName$</AlertParameter2>

    </AlertParameters>

  </AlertSettings>

  <OperationalStates>

    <OperationalState ID="UnderWarningThresholds" MonitorTypeStateID="UnderWarningThresholds" HealthState="Success"/>

    <OperationalState ID="OverWarningUnderErrorThresholds" MonitorTypeStateID="OverWarningUnderErrorThresholds" HealthState="Warning"/>

    <OperationalState ID="OverErrorThresholds" MonitorTypeStateID="OverErrorThresholds" HealthState="Error"/>

  </OperationalStates>

  <Configuration>

    <ComputerName>$Target/Host/Property[Type="Windows!Microsoft.Windows.Computer"]/NetworkName$</ComputerName>

    <DiskLabel>$Target/Property[Type="Windows!Microsoft.Windows.LogicalDevice"]/DeviceID$</DiskLabel>

    <IntervalSeconds>900</IntervalSeconds>

    <SystemDriveWarningMBytesThreshold>500</SystemDriveWarningMBytesThreshold>

    <SystemDriveWarningPercentThreshold>10</SystemDriveWarningPercentThreshold>

    <SystemDriveErrorMBytesThreshold>300</SystemDriveErrorMBytesThreshold>

    <SystemDriveErrorPercentThreshold>5</SystemDriveErrorPercentThreshold>

    <NonSystemDriveWarningMBytesThreshold>2000</NonSystemDriveWarningMBytesThreshold>

    <NonSystemDriveWarningPercentThreshold>10</NonSystemDriveWarningPercentThreshold>

    <NonSystemDriveErrorMBytesThreshold>1000</NonSystemDriveErrorMBytesThreshold>

    <NonSystemDriveErrorPercentThreshold>5</NonSystemDriveErrorPercentThreshold>

    <NumSamples>4</NumSamples>

  </Configuration>

</UnitMonitor>