eG Monitoring
 

Measures reported by LSArchivingTest

Archiving in Lync Server 2013 provides a way for you to archive communications that are sent through Lync Server 2013. The following types of content can be archived:

  • Peer-to-peer instant messages
  • Conferences (meetings), which are multiparty instant messages
  • Conference content, including uploaded content (for example, handouts) and event-related content (for example, joining, leaving, uploading sharing, and changes in visibility)
  • Whiteboards and polls shared during a conference
Archiving is automatically installed on each Front End Server when you deploy the server, but Archiving is not enabled until you configure it. The Archiving feature includes the following components:

Archiving agents. Archiving agents (also known as unified data collection agents) are installed and activated automatically on every Front End pool and Standard Edition server. Although archiving agents are activated automatically, no messages are actually captured until Archiving is enabled and appropriately configured.

Archiving data storage. Data storage for Lync Server 2013 can be either of the following:

  • Archiving using Microsoft Exchange integration. If you have users who are homed on Exchange 2013 and their mailboxes have been put on In-Place Hold, you can select the option to integrate Lync Server 2013 storage with Exchange storage. If you choose the Microsoft Exchange integration option, you use Exchange 2013 policies and configurations to control the archiving of Lync Server 2013 data for those users.
  • Archiving using Lync Server Archiving databases. If you have users who are not homed on Exchange 2013 or who have not had their mailboxes put on In-Place Hold, or if you don’t want to use Microsoft Exchange integration for any or all users in your deployment, you can deploy Lync Server Archiving databases using SQL Server to store Archiving data for those users. In this case, Lync Server 2013 Archiving policies and configurations determine whether Archiving is enabled and how it is implemented. To use Lync Server 2013, you must add the appropriate SQL Server databases to your topology and publish the topology.
This test monitors the archiving pattern of the Microsoft Lync and provides you with the numerical statistics of the following information:
  • The messages that failed validation
  • The messages that were dropped
  • The messages that failed to be written to the backend database server and
  • The messages that were sent for archiving.
Using this test, administrators can easily identify technical glitches in the Microsoft Lync that caused issues which eventually led to validation failure of messages, drop in the messages etc.

The measures made by this test are as follows:

Measurement Description Measurement Unit Interpretation
Validation_failed_msg Indicates the number of messages that failed validation. Number A low value is desired for this measure. A rapid increase in the value of this measure may indicate the presence of malformed messages in the message queue.
Dropped_msg_MQ Indiactes the number of messages that were dropped from the MSMQ queue. Number  
Msg_failed_towriteDb Indicates the number of messages that failed to be written to the backend database server. Number A low value is desired for this measure. A sudden/gradual increase in this value is a cause of concern which clearly indicates the failure of the service that is responsible for writing the messages to the database.
ArchMsg Indicates the number of messages that were sent for archiving to the Archiving Message queue. Number A high value is desired for this measure.