Home
  •  

Disk Read Latency

Microsoft.SQLServer.2012.Database.DiskReadLatencyMonitor (UnitMonitor)

Disk Read Latency monitor for 2012 DBs

Knowledge Base article:

Summary

The monitor checks latency for the disk read operation and throws an alert.

This alert indicates that the average time that it takes to read data from the disk has stayed greater than threshold during an interval.

Causes

The problem may be caused by a disk bottleneck or disk contention.

Resolutions

To resolve this error, do one or more of the following:

SQL Server Best Practices Article (Disk Configuration Best Practices & Common Pitfalls)

http://go.microsoft.com/fwlink/?LinkId=789184

Overrideable Parameters

Name

Description

Default Value

Alert Priority

Defines Alert Priority.

Normal

Alert Severity

Defines Alert Severity.

Error

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.

300

Number of samples

If the parameter threshold exceeding count is greater or equal to the number of samples, then the monitor will be in a bad state

6

Synchronization Time

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

00:04

Threshold

Threshold

40

Timeout (seconds)

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

200

Element properties:

TargetMicrosoft.SQLServer.2012.Database
Parent MonitorSystem.Health.PerformanceState
CategoryPerformanceHealth
EnabledFalse
Alert GenerateTrue
Alert SeverityError
Alert PriorityNormal
Alert Auto ResolveTrue
Monitor TypeMicrosoft.SQLServer.2012.Database.DiskReadLatency.MonitorType
RemotableTrue
AccessibilityPublic
Alert Message
SQL DB 2012 disk read latency is too high
The database "{0}" in SQL instance "{1}" on computer "{2}" mount point "{3}" has too high disk read latency "{4}". See "alert context" tab for more details.
RunAsDefault

Source Code:

<UnitMonitor ID="Microsoft.SQLServer.2012.Database.DiskReadLatencyMonitor" Accessibility="Public" Enabled="false" Target="SQL2012Core!Microsoft.SQLServer.2012.Database" ParentMonitorID="SystemHealth!System.Health.PerformanceState" Remotable="true" Priority="Normal" TypeID="Microsoft.SQLServer.2012.Database.DiskReadLatency.MonitorType" ConfirmDelivery="false">

  <Category>PerformanceHealth</Category>

  <AlertSettings AlertMessage="Microsoft.SQLServer.2012.Database.DiskReadLatencyMonitor.AlertMessage">

    <AlertOnState>Error</AlertOnState>

    <AutoResolve>true</AutoResolve>

    <AlertPriority>Normal</AlertPriority>

    <AlertSeverity>Error</AlertSeverity>

    <AlertParameters>

      <AlertParameter1>$Target/Property[Type="SQL!Microsoft.SQLServer.Database"]/DatabaseName$</AlertParameter1>

      <AlertParameter2>$Target/Host/Property[Type="SQL!Microsoft.SQLServer.ServerRole"]/InstanceName$</AlertParameter2>

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

      <AlertParameter4>$Data/Context/ObjectName$</AlertParameter4>

      <AlertParameter5>$Data/Context/SampleValue$</AlertParameter5>

    </AlertParameters>

  </AlertSettings>

  <OperationalStates>

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

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

  </OperationalStates>

  <Configuration>

    <IntervalSeconds>300</IntervalSeconds>

    <TimeoutSeconds>200</TimeoutSeconds>

    <Threshold>40</Threshold>

    <NumSamples>6</NumSamples>

    <SyncTime/>

  </Configuration>

</UnitMonitor>