Universal Linux Logical Disk Free Space Monitor
The amount of free space on the logical disk (file system) is low. System performance may be adversely affected, and the ability to add or modify existing files on the file system may be at risk until additional free space is made available.
The file system space reserved for the root user is not included in the calculated free space. File system space usage is calculated with current free and total values, which may not accurately represent true usage for file systems that dynamically allocate space, such as ZFS.
The monitor threshold is analyzed against an average of values returned in polls to the agent, where the Number of Samples parameter controls the number of samples included in the calculation of the average.
Separate threshold values can be set for Warning and Error states. Since file systems may vary in size from a few gigabytes to many terabytes, the Logical Disk Free Space monitor requires that an Operator indicate both the megabyte and percentage threshold values. Both megabyte and percentage thresholds must be passed before the Warning and Error thresholds are reached.
This monitor is disabled by default. It can be enabled with an override, targeting specific Logical Disk instances or all Logical Disk instances. If this monitor is enabled, the Logical Disk % Free Space monitor should be disabled with an override.
Default Configuration
Parameter | Default Value |
Error Mbytes Threshold | 1000 |
Error Percent Threshold | 5 |
Warning Mbytes Threshold | 2000 |
Warning Percent Threshold | 10 |
Interval (seconds) | 300 |
Number of Samples | 1 |
Overrides can be used to change the parameter values defined above for all instances or for specific instances or groups.
When existing files grow in size and the new files are added, the free space is taken up on a file system. When the amount of free space on the file system falls below the threshold, the state for the Logical Disk will change.
To increase the amount of available space, do one or more of the following:
View the disk capacity from the Operations Manager console. Determine if any new applications have been recently installed.
Review any log files for logs that appear to be excessively large. If so, determine if the logs are current or historical logs. Consider creating compressed archives of historical log files.
Back up and remove files, or delete unnecessary files from the file system.
Move files to another file system or to offline storage.
Add storage capacity.
To view recent file system capacity history you can use the following view:
Disk Capacity
Target | Microsoft.Linux.Universal.LogicalDisk | ||
Parent Monitor | System.Health.AvailabilityState | ||
Category | AvailabilityHealth | ||
Enabled | False | ||
Alert Generate | True | ||
Alert Severity | MatchMonitorHealth | ||
Alert Priority | Normal | ||
Alert Auto Resolve | True | ||
Monitor Type | Microsoft.Unix.WSMan.LogicalDisk.FreeSpace.MonitorType | ||
Remotable | True | ||
Accessibility | Public | ||
Alert Message |
| ||
RunAs | Default |
<UnitMonitor ID="Microsoft.Linux.Universal.LogicalDisk.FreeSpace.Monitor" Accessibility="Public" Target="Universal!Microsoft.Linux.Universal.LogicalDisk" TypeID="Unix!Microsoft.Unix.WSMan.LogicalDisk.FreeSpace.MonitorType" Enabled="false" ParentMonitorID="SystemHealth!System.Health.AvailabilityState">
<Category>AvailabilityHealth</Category>
<AlertSettings AlertMessage="Microsoft.Linux.Universal.LogicalDisk.FreeSpace.AlertMessage">
<AlertOnState>Warning</AlertOnState>
<AutoResolve>true</AutoResolve>
<AlertPriority>Normal</AlertPriority>
<AlertSeverity>MatchMonitorHealth</AlertSeverity>
<AlertParameters>
<AlertParameter1>$Data/Context/WsManData/*[local-name(.)='SCX_FileSystemStatisticalInformation']/*[local-name(.)='PercentFreeSpace']$</AlertParameter1>
<AlertParameter2>$Data/Context/WsManData/*[local-name(.)='SCX_FileSystemStatisticalInformation']/*[local-name(.)='FreeMegabytes']$</AlertParameter2>
</AlertParameters>
</AlertSettings>
<OperationalStates>
<OperationalState HealthState="Error" MonitorTypeStateID="UnderErrorThreshold" ID="UnderErrorThreshold"/>
<OperationalState HealthState="Warning" MonitorTypeStateID="UnderWarningThreshold" ID="UnderWarningThreshold"/>
<OperationalState HealthState="Success" MonitorTypeStateID="OverThreshold" ID="OverThreshold"/>
</OperationalStates>
<Configuration>
<TargetSystem>$Target/Host/Property[Type="Unix!Microsoft.Unix.Computer"]/NetworkName$</TargetSystem>
<Uri>http://schemas.microsoft.com/wbem/wscim/1/cim-schema/2/SCX_FileSystemStatisticalInformation?__cimnamespace=root/scx</Uri>
<Filter/>
<SplitItems>true</SplitItems>
<Interval>300</Interval>
<InstanceName>$Target/Property[Type="Unix!Microsoft.Unix.LogicalDevice"]/DeviceID$</InstanceName>
<ErrorPctThreshold>5</ErrorPctThreshold>
<ErrorMBThreshold>1000</ErrorMBThreshold>
<WarningPctThreshold>10</WarningPctThreshold>
<WarningMBThreshold>2000</WarningMBThreshold>
</Configuration>
</UnitMonitor>