Data Collection Agent: Number of critical messages that could not be enqueued into LYSS and were dropped by the dispatcher queue Monitor

  • ID:  Microsoft.LS.2015.Monitoring.UnitMonitor.ThresholdPC.Registrar.PERF_DATACOLLECTION_AgentDispatcherQueue_CRITICAL_MESSAGES_DROPPED_SEC
  • Description:  Data Collection Agent: Number of critical messages that could not be enqueued into LYSS and were dropped by the dispatcher queue
  • Target:  Dispatcher Queue Dependency for Component Registrar
  • Enabled:  Yes

Operational States

Name State Description
Over Threshold state for Monitor 'Data Collection Agent: Number of critical messages that could not be enqueued into LYSS and were dropped by the dispatcher queue' Error  
Under Threshold state for Monitor 'Data Collection Agent: Number of critical messages that could not be enqueued into LYSS and were dropped by the dispatcher queue' Success  
Under Threshold Over Threshold state for Monitor 'Data Collection Agent: Number of critical messages that could not be enqueued into LYSS and were dropped by the dispatcher queue' Warning  

Overridable Parameters

Parameter Name Default Value Description Override
Frequency 60 Frequency
Warning Threshold 1 Warning Threshold
Error Threshold 100 Error Threshold

Alert Details

Monitor State Message Priority Severity Auto Resolution
Over Threshold state for Monitor 'Data Collection Agent: Number of critical messages that could not be enqueued into LYSS and were dropped by the dispatcher queue' (Error) [Skype] The per-second critical message drop rate of the dispatcher queue. Medium Critical Yes

Run As Profiles

Name
Default

Monitor Knowledgebase

Summary

The per-second critical message drop rate of the dispatcher queue.

Causes

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.

Resolutions

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.

External References
This monitor does not contain any external references.

See Also for Lync Server 2015 Monitoring Management Pack


Downloads for Lync Server 2015 Monitoring Management Pack

AZURE OPTIMIZATION ASSESSMENT GET STARTED
MIGRATION TO AZURE GET STARTED
SYSTEM CENTER MIGRATION TO AZURE GET STARTED
MIGRATION TO AZURE FOR SQL AND WINDOWS 2008 GET STARTED