Archiving Server : Archiving Server enable you to archive IM communications and meeting content for compliance reasons. If you do not have legal compliance concerns, you do not need to deploy Archiving Server. An SQL Server Back End Server is required to implement Archiving.
Monitoring Server : Monitoring Server collects data about the quality of your network media, in both Enterprise voice calls and A/V conferences. It also collects call error records (CERs), which you can use to troubleshoot failed calls. Additionally, it collects usage information in the form of call detail records (CDRs) about various Lync Server features so that you can calculate return on investment of your deployment and plan the future growth of your deployment. A monitoring server role can be deployed to collect statistical usage metrics for IM, conferencing and Enterprise voice by tracking call detail records. Monitoring Server is typically collocated with the Microsoft Lync Server 2010, Archiving Server. An SQL Server Back End Server is required to implement a Monitoring Server.
Discovery with the agent
Collector Type: Agent
Category: Application Monitors
Application Name: Microsoft Lync Archiving and Monitoring Servers
Global Template Name : Microsoft Lync Archiving and Monitoring Servers DotNet v4
Pre-requisites : For Lync monitors need Microsoft .NET Framework 4.
|Metric Name||Display Name||Description|
|MSMQService_totalmessagesinallqueues||MSMQService_totalmessagesinallqueues||The size of the queue will vary depending on load. Verify that the queue is not increasing unbounded. Establish a baseline for the counter, and monitor the counter to ensure that it does not exceed that baseline.|
|QMS_MessageTransactionsFailed||QMS_MessageTransactionsFailed||This counter represents the total number of message queue/database transactions that failed since the server was started. A large number of database transactions have failed.|
|Arch_service_NumberOfArchivingMessagesThatFailedValidation||Arch_service_NumberOfArchivingMessagesThatFailedValidation||Per second rate of messages that validation failed for. This may be caused if there is a version mismatch between server and the agent or if malformed messages are present in the message queue.|
|Arch_service_RateOfArchivingMessagesThatWereDroppedFromMessageQueuing||Arch_service_RateOfArchivingMessagesThatWereDroppedFromMessageQueuing||Per second rate of dropped messages from MSMQ queue. This may be caused if there is a version mismatch between server and the agent or if malformed messages are present in the message queue.|
|Arch_service_RateOfArchivingMessagesThatWereNotWrittenToTheDatabase||Arch_service_RateOfArchivingMessagesThatWereNotWrittenToTheDatabase||Per second rate of messages failed to be written to SQL database. This could happen if the service failed to write a critical message to the back end SQL server.|