Home
  •  

Data Collection Agent: Number of messages blocked

Microsoft.LS.2015.Monitoring.UnitMonitor.ThresholdPC.Registrar.PERF_DATACOLLECTION_Agent_IM_BLOCKED_SEC (UnitMonitor)

Knowledge Base article:

Summary

Number of IM messages blocked per second in critical archiving mode due to local Storage Service health and connectivity issues.

Causes

This can occur due to server overload, Storage Service connectivity issues, or internal errors.

Resolutions

The server will continue to block messages for compliance purposes until the root cause is of the issue is resolved. Typically, this situation occurs due to server overload and an inability to enqueue items into Storage Service. 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 blocking of messages.

Element properties:

TargetMicrosoft.LS.2015.Component.Registrar
Parent MonitorSystem.Health.PerformanceState
CategoryPerformanceHealth
EnabledTrue
Alert GenerateTrue
Alert SeverityError
Alert PriorityNormal
Alert Auto ResolveTrue
Monitor TypeMicrosoft.LS.2015.Performance.Double.DeltaThresholdMonitor
RemotableTrue
AccessibilityPublic
Alert Message
[Skype] Number of IM messages blocked per second in critical archiving mode due to local Storage Service health and connectivity issues.
Perf Object Name:
Perf Counter Name: {0}
Perf Counter Value: {1}
Error Threshold: 50
Warning Threshold: 1
Delta Window Size: 2

Please see the 'Product Knowledge' and the 'Alert Context' tab on Alert Properties view for more information.
RunAsDefault

Source Code:

<UnitMonitor ID="Microsoft.LS.2015.Monitoring.UnitMonitor.ThresholdPC.Registrar.PERF_DATACOLLECTION_Agent_IM_BLOCKED_SEC" Accessibility="Public" Enabled="true" Target="Microsoft.LS.2015.Component.Registrar" ParentMonitorID="Health!System.Health.PerformanceState" Remotable="true" Priority="Normal" TypeID="Microsoft.LS.2015.Performance.Double.DeltaThresholdMonitor" ConfirmDelivery="false">

  <Category>PerformanceHealth</Category>

  <AlertSettings AlertMessage="Alert_Number_of_IM_messages_blocked_per_second_in_critical_archiving_mode_due_to_local_Storage_Service_health_and_connectivity_issues.">

    <AlertOnState>Error</AlertOnState>

    <AutoResolve>true</AutoResolve>

    <AlertPriority>Normal</AlertPriority>

    <AlertSeverity>Error</AlertSeverity>

    <AlertParameters>

      <AlertParameter1>$Data/Context/CounterName$</AlertParameter1>

      <AlertParameter2>$Data/Context/Value$</AlertParameter2>

    </AlertParameters>

  </AlertSettings>

  <OperationalStates>

    <OperationalState ID="Microsoft.LS.2015.Monitoring.UnitMonitor.ThresholdPC.Registrar.PERF_DATACOLLECTION_Agent_IM_BLOCKED_SEC_OverThreshold" MonitorTypeStateID="OverThreshold" HealthState="Error"/>

    <OperationalState ID="Microsoft.LS.2015.Monitoring.UnitMonitor.ThresholdPC.Registrar.PERF_DATACOLLECTION_Agent_IM_BLOCKED_SEC_UnderThreshold" MonitorTypeStateID="UnderThreshold" HealthState="Success"/>

    <OperationalState ID="Microsoft.LS.2015.Monitoring.UnitMonitor.ThresholdPC.Registrar.PERF_DATACOLLECTION_Agent_IM_BLOCKED_SEC_UnderThresholdOverThreshold" MonitorTypeStateID="UnderThresholdOverThreshold" HealthState="Warning"/>

  </OperationalStates>

  <Configuration>

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

    <CounterName>UDC - Number of IM Messages Blocked per second</CounterName>

    <ObjectName>LS:DATACOLLECTION - Data Collection Agent</ObjectName>

    <InstanceName/>

    <AllInstances>false</AllInstances>

    <Frequency>60</Frequency>

    <WarningThreshold>1</WarningThreshold>

    <ErrorThreshold>50</ErrorThreshold>

    <NumSamples>2</NumSamples>

  </Configuration>

</UnitMonitor>