DB FILESTREAM Filegroup Free Space

Microsoft.SQLServer.Windows.Monitor.DBFilegroupFd.GroupSpace (UnitMonitor)

The monitor reports a warning when the free space drops below the Warning Threshold setting, expressed as percentage of the sum of data size. The monitor reports a critical alert when the free space drops below the Critical Threshold. Note that this monitor is disabled by default. Use overrides to enable it when necessary.

Knowledge Base article:

Summary

The monitor reports a warning when the available disk space for the FILESTREAM Filegroup Container drops below the Warning Threshold value expressed as percentage of the disk free space total. The monitor reports a critical alert when the free space drops below the Critical Threshold.

The FILESTREAM Filegroup data container folder typically grows over time while more data is added into the tables. Therefore, administrators will wish to monitor this parameter to ensure there is sufficient space remaining in the storage location for the container folder.

Note that monitoring of database filegroups issues alerts only when free space is depleted in all of the groups altogether; alerts will not be issued if one (or some) of the database filegroups have reached the space limit. To receive alerts if one (or some) of the database filegroups have reached the space limit, enable discovery of filegroups and files, and also enable free space for containers monitoring.

Causes

When the available disk space on the drive where the FILESTREAM data container is configured becomes too low, some failures may occur preventing successful processing of data, delaying user’s queries, or affecting other applications sharing the same allocation of the disk space.

Resolutions

The resolution(s) for low available disk space depend upon the root causes, which must be investigated in each case when this issue occurs. The condition may be alleviated by any of the following potential approaches:

Overridable Parameters

Name

Description

Default Value

Alert Priority

Defines Alert Priority.

Normal

Alert Severity

Defines Alert Severity.

Match monitor’s health

Azure Maximum File Size (MB)

The maximum size of data file stored in Azure BLOB Storage. The workflow will consider this value as a maximum storage capacity for each file.

1048576

Critical Threshold

The monitor will change its state to Critical if the value drops below this threshold. Being between this threshold and the warning threshold (inclusive) will result in the monitor being in a warning state.

10

Enabled

Enables or disables the workflow.

No

Generates Alerts

Defines whether the workflow generates an Alert.

Yes

Interval (seconds)

The recurring interval of time in seconds in which to run the workflow.

900

Synchronization Time

The synchronization time specified by using a 24-hour format. May be omitted.

 

Timeout (seconds)

Specifies the time the workflow is allowed to run before being closed and marked as failed.

300

Timeout for query execution (seconds)

The workflow will fail and register an event, if the query execution takes longer than the specified period.

60

Timeout for database connection (seconds)

The workflow will fail and register an event, if it cannot access the database during the specified period.

15

Warning Threshold

The monitor will change its state to Warning if the value drops below this threshold.

20

Element properties:

TargetMicrosoft.SQLServer.Windows.DBFilegroupFd
Parent MonitorSystem.Health.PerformanceState
CategoryPerformanceHealth
EnabledFalse
Alert GenerateTrue
Alert SeverityMatchMonitorHealth
Alert PriorityNormal
Alert Auto ResolveTrue
Monitor TypeMicrosoft.SQLServer.Windows.MonitorType.DBFilegroupFd.GroupSpace
RemotableTrue
AccessibilityPublic
Alert Message
MSSQL on Windows: DB FILESTREAM Filegroup data container is running out of space
The DB FILESTREAM Filegroup data container for Filegroup "{2}" on database "{3}" on SQL Server instance "{1}", computer "{0}" is running out of space. See the knowledge section for more details.
RunAsDefault

Source Code:

<UnitMonitor ID="Microsoft.SQLServer.Windows.Monitor.DBFilegroupFd.GroupSpace" Accessibility="Public" Enabled="false" Target="SqlDiscW!Microsoft.SQLServer.Windows.DBFilegroupFd" ParentMonitorID="Health!System.Health.PerformanceState" Remotable="true" Priority="Normal" TypeID="Microsoft.SQLServer.Windows.MonitorType.DBFilegroupFd.GroupSpace" ConfirmDelivery="true">
<Category>PerformanceHealth</Category>
<AlertSettings AlertMessage="Microsoft.SQLServer.Windows.Monitor.DBFilegroupFd.GroupSpace.AlertMessage">
<AlertOnState>Error</AlertOnState>
<AutoResolve>true</AutoResolve>
<AlertPriority>Normal</AlertPriority>
<AlertSeverity>MatchMonitorHealth</AlertSeverity>
<AlertParameters>
<AlertParameter1>$Target/Host/Host/Property[Type="SqlCoreLib!Microsoft.SQLServer.Core.DBEngine"]/MachineName$</AlertParameter1>
<AlertParameter2>$Target/Host/Host/Property[Type="SqlCoreLib!Microsoft.SQLServer.Core.DBEngine"]/InstanceName$</AlertParameter2>
<AlertParameter3>$Target/Property[Type="SqlCoreLib!Microsoft.SQLServer.Core.Filegroup"]/GroupName$</AlertParameter3>
<AlertParameter4>$Target/Host/Property[Type="SqlCoreLib!Microsoft.SQLServer.Core.Database"]/DatabaseName$</AlertParameter4>
</AlertParameters>
</AlertSettings>
<OperationalStates>
<OperationalState ID="UnderThreshold1" MonitorTypeStateID="UnderThreshold1" HealthState="Error"/>
<OperationalState ID="OverThreshold1UnderThreshold2" MonitorTypeStateID="OverThreshold1UnderThreshold2" HealthState="Warning"/>
<OperationalState ID="OverThreshold2" MonitorTypeStateID="OverThreshold2" HealthState="Success"/>
</OperationalStates>
<Configuration>
<MachineName>$Target/Host/Host/Property[Type="SqlCoreLib!Microsoft.SQLServer.Core.DBEngine"]/MachineName$</MachineName>
<NetbiosComputerName>$Target/Host/Host/Property[Type="SqlCoreLib!Microsoft.SQLServer.Core.DBEngine"]/NetbiosComputerName$</NetbiosComputerName>
<InstanceName>$Target/Host/Host/Property[Type="SqlCoreLib!Microsoft.SQLServer.Core.DBEngine"]/InstanceName$</InstanceName>
<DatabaseName>$Target/Host/Property[Type="SqlCoreLib!Microsoft.SQLServer.Core.Database"]/DatabaseName$</DatabaseName>
<FilegroupName>$Target/Property[Type="SqlCoreLib!Microsoft.SQLServer.Core.Filegroup"]/GroupName$</FilegroupName>
<AzureMaxFileSizeMB>1048576</AzureMaxFileSizeMB>
<ObjectName>SQL DB FileStream FileGroup</ObjectName>
<CounterName>DB FileStrem FileGroup Free Space (%)</CounterName>
<PerfInstanceName/>
<ValuePropertyName>FreeSpacePercentMon</ValuePropertyName>
<Threshold1>10</Threshold1>
<Threshold2>20</Threshold2>
<ConnectionString>$Target/Host/Host/Property[Type="SqlCoreLib!Microsoft.SQLServer.Core.DBEngine"]/ConnectionString$</ConnectionString>
<InstanceVersion>$Target/Host/Host/Property[Type="SqlCoreLib!Microsoft.SQLServer.Core.DBEngine"]/Version$</InstanceVersion>
<InstanceEdition>$Target/Host/Host/Property[Type="SqlCoreLib!Microsoft.SQLServer.Core.DBEngine"]/Edition$</InstanceEdition>
<MonitoringType>$Target/Host/Host/Property[Type="SqlDiscW!Microsoft.SQLServer.Windows.DBEngine"]/MonitoringType$</MonitoringType>
<SqlExecTimeoutSeconds>60</SqlExecTimeoutSeconds>
<SqlTimeoutSeconds>15</SqlTimeoutSeconds>
<TimeoutSeconds>300</TimeoutSeconds>
<IntervalSeconds>900</IntervalSeconds>
<SyncTime/>
</Configuration>
</UnitMonitor>