Windows DNS Server 2016 和 1709+ Cache Limit Hit

Microsoft.Windows.DNSServer.2016.Monitor.CacheLimitHit (UnitMonitor)

監視已設定的快取大小

Knowledge Base article:

摘要

此事件型監視器會監視已設定的快取限制。

原因

警告狀態

由識別碼為 7688 的事件觸發。原因:DNS 伺服器上的快取大小接近其已設定的限制。遞迴執行緒已觸發事件來將快取大小降低至所設定的限制內。系統可能會經歷短暫的 CPU 尖峰。

重大狀態

由識別碼為 7689 的事件觸發。原因:DNS 伺服器上的快取大小接近其已設定的限制。逾時執行緒已開始將快取大小降低至所設定的限制內。系統可能會經歷短暫的 CPU 尖峰。

狀況良好狀態可能由識別碼為 7690 的事件觸發:DNS 伺服器上的快取大小已降低至其已設定的限制內。

解決方式

DNS 伺服器將會自動進行清理,如有需要,將會排清快取,使其降至設定的限制之內。使用者可能會因此經歷 CPU 尖峰。如果此錯誤的發生頻繁太高,則請檢查所設定的快取限制。如果該限制對您的部署而言太低,請做相應的變更。

Element properties:

TargetMicrosoft.Windows.DNSServer.2016.Server
Parent MonitorSystem.Health.AvailabilityState
CategoryAvailabilityHealth
EnabledTrue
Alert GenerateTrue
Alert SeverityMatchMonitorHealth
Alert PriorityNormal
Alert Auto ResolveTrue
Monitor TypeMicrosoft.Windows.3SingleEventLog3StateUnitMonitorType
RemotableTrue
AccessibilityPublic
Alert Message
Windows DNS Server 2016 和 1709+ - Cache Limit Hit 監視器警示

事件識別碼:{0}
事件來源:{1}
事件記錄檔:{2}
事件描述:{3}
RunAsMicrosoft.Windows.DNSServer.2016.ActionAccount

Source Code:

<UnitMonitor ID="Microsoft.Windows.DNSServer.2016.Monitor.CacheLimitHit" Accessibility="Public" Enabled="true" Target="Microsoft.Windows.DNSServer.2016.Server" ParentMonitorID="Health!System.Health.AvailabilityState" Remotable="true" Priority="Normal" RunAs="Microsoft.Windows.DNSServer.2016.ActionAccount" TypeID="Windows!Microsoft.Windows.3SingleEventLog3StateUnitMonitorType" ConfirmDelivery="true">
<Category>AvailabilityHealth</Category>
<AlertSettings AlertMessage="Microsoft.Windows.DNSServer.2016.Monitor.CacheLimitHit_AlertMessageResourceID">
<AlertOnState>Warning</AlertOnState>
<AutoResolve>true</AutoResolve>
<AlertPriority>Normal</AlertPriority>
<AlertSeverity>MatchMonitorHealth</AlertSeverity>
<AlertParameters>
<AlertParameter1>$Data/Context/EventDisplayNumber$</AlertParameter1>
<AlertParameter2>$Data/Context/EventSourceName$</AlertParameter2>
<AlertParameter3>$Data/Context/Channel$</AlertParameter3>
<AlertParameter4>$Data/Context/EventDescription$</AlertParameter4>
</AlertParameters>
</AlertSettings>
<OperationalStates>
<OperationalState ID="WarningState" MonitorTypeStateID="FirstEventRaised" HealthState="Warning"/>
<OperationalState ID="ErrorState" MonitorTypeStateID="SecondEventRaised" HealthState="Error"/>
<OperationalState ID="SuccessState" MonitorTypeStateID="ThirdEventRaised" HealthState="Success"/>
</OperationalStates>
<Configuration>
<FirstComputerName>$Target/Host/Property[Type="Windows!Microsoft.Windows.Computer"]/NetworkName$</FirstComputerName>
<FirstLogName>DNS Server</FirstLogName>
<FirstExpression>
<SimpleExpression>
<ValueExpression>
<XPathQuery Type="UnsignedInteger">EventDisplayNumber</XPathQuery>
</ValueExpression>
<Operator>Equal</Operator>
<ValueExpression>
<Value Type="UnsignedInteger">7688</Value>
</ValueExpression>
</SimpleExpression>
</FirstExpression>
<SecondComputerName>$Target/Host/Property[Type="Windows!Microsoft.Windows.Computer"]/NetworkName$</SecondComputerName>
<SecondLogName>DNS Server</SecondLogName>
<SecondExpression>
<SimpleExpression>
<ValueExpression>
<XPathQuery Type="UnsignedInteger">EventDisplayNumber</XPathQuery>
</ValueExpression>
<Operator>Equal</Operator>
<ValueExpression>
<Value Type="UnsignedInteger">7689</Value>
</ValueExpression>
</SimpleExpression>
</SecondExpression>
<ThirdComputerName>$Target/Host/Property[Type="Windows!Microsoft.Windows.Computer"]/NetworkName$</ThirdComputerName>
<ThirdLogName>DNS Server</ThirdLogName>
<ThirdExpression>
<SimpleExpression>
<ValueExpression>
<XPathQuery Type="UnsignedInteger">EventDisplayNumber</XPathQuery>
</ValueExpression>
<Operator>Equal</Operator>
<ValueExpression>
<Value Type="UnsignedInteger">7690</Value>
</ValueExpression>
</SimpleExpression>
</ThirdExpression>
</Configuration>
</UnitMonitor>