The total number of non-critical messages dropped by the dispatcher queue.
This can occur due to server overload, Storage Service connectivity issues, or internal errors. Generally, Storage Service or its dependent components is the cause of the slow or blocked processing resulting in dropped messages.
An immediate investigation to find the root cause of this torpid processing of the data by Storage Service or its dependent components is required in order to prevent further data loss and return to a normal state. Looking for error events from the Storage Service will provide a good start to the investigation. Taking this server out of rotation might be necessary to prevent further data loss, to help buy more time to resolve the root cause of the issue and to let the dispatcher queue reduce its backlog.
Target | Microsoft.LS.2019.Component.Registrar | ||
Parent Monitor | System.Health.PerformanceState | ||
Category | PerformanceHealth | ||
Enabled | True | ||
Alert Generate | True | ||
Alert Severity | Error | ||
Alert Priority | High | ||
Alert Auto Resolve | True | ||
Monitor Type | Microsoft.LS.2019.Performance.Double.DeltaThresholdMonitor | ||
Remotable | True | ||
Accessibility | Public | ||
Alert Message |
| ||
RunAs | Default |
<UnitMonitor ID="Microsoft.LS.2019.Monitoring.UnitMonitor.ThresholdPC.Registrar.PERF_DATACOLLECTION_AgentDispatcherQueue_NON_CRITICAL_MESSAGES_DROPPED" Accessibility="Public" Enabled="true" Target="SFBDiscovery!Microsoft.LS.2019.Component.Registrar" ParentMonitorID="Health!System.Health.PerformanceState" Remotable="true" Priority="Normal" TypeID="Microsoft.LS.2019.Performance.Double.DeltaThresholdMonitor" ConfirmDelivery="false">
<Category>PerformanceHealth</Category>
<AlertSettings AlertMessage="Alert_The_total_number_of_non_critical_messages_dropped_by_the_dispatcher_queue.">
<AlertOnState>Error</AlertOnState>
<AutoResolve>true</AutoResolve>
<AlertPriority>High</AlertPriority>
<AlertSeverity>Error</AlertSeverity>
<AlertParameters>
<AlertParameter1>$Data/Context/CounterName$</AlertParameter1>
<AlertParameter2>$Data/Context/Value$</AlertParameter2>
</AlertParameters>
</AlertSettings>
<OperationalStates>
<OperationalState ID="Microsoft.LS.2019.Monitoring.UnitMonitor.ThresholdPC.Registrar.PERF_DATACOLLECTION_AgentDispatcherQueue_NON_CRITICAL_MESSAGES_DROPPED_OverThreshold" MonitorTypeStateID="OverThreshold" HealthState="Error"/>
<OperationalState ID="Microsoft.LS.2019.Monitoring.UnitMonitor.ThresholdPC.Registrar.PERF_DATACOLLECTION_AgentDispatcherQueue_NON_CRITICAL_MESSAGES_DROPPED_UnderThreshold" MonitorTypeStateID="UnderThreshold" HealthState="Success"/>
<OperationalState ID="Microsoft.LS.2019.Monitoring.UnitMonitor.ThresholdPC.Registrar.PERF_DATACOLLECTION_AgentDispatcherQueue_NON_CRITICAL_MESSAGES_DROPPED_UnderThresholdOverThreshold" MonitorTypeStateID="UnderThresholdOverThreshold" HealthState="Warning"/>
</OperationalStates>
<Configuration>
<ComputerName>$Target/Host/Host/Host/Property[Type="Windows!Microsoft.Windows.Computer"]/NetworkName$</ComputerName>
<CounterName>UDC - Number of Non-Critical Messages Dropped</CounterName>
<ObjectName>LS:DATACOLLECTION - Dispatcher Queues in the Data Collection Agent</ObjectName>
<AllInstances>true</AllInstances>
<Frequency>900</Frequency>
<IncludeInstances>
<RegExExpression>
<ValueExpression>
<XPathQuery Type="String">InstanceName</XPathQuery>
</ValueExpression>
<Operator>MatchesWildcard</Operator>
<Pattern>_Total</Pattern>
</RegExExpression>
</IncludeInstances>
<ExcludeInstances/>
<WarningThreshold>250</WarningThreshold>
<ErrorThreshold>500</ErrorThreshold>
<NumSamples>2</NumSamples>
</Configuration>
</UnitMonitor>