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: SharePoint-2007
Global Template Name : Microsoft SharePoint 2007 Performance Counters DotNet v4*
Pre-requisites : For MSSQL 2016 monitors need Microsoft .Net Framework 4.0.
|Metric Name||Display Name||Description||netclrdata.sqlclienttotalnumberfailedconnects||NETCLRData SqlClientTotalNumberfailedconnects||The total number of connection open attempts that have failed for any reason.|
|pagingfile.percentusage||PagingFile PercentUsage||The amount of the Page File instance in use in percent.|
|processor.percentprocessortime||Processor PercentProcessorTime||% Processor Time is the percentage of elapsed time that the processor spends to execute a nonIdle thread. It is calculated by measuring the percentage of time that the processor spends executing the idle thread and then subtracting that value from 100%.|
|networkinterface.outputqueuelength||NetworkInterface OutputQueueLength||Output Queue Length is the length of the output packet queue (in packets). If this is longer than two, there are delays and the bottleneck should be found and eliminated, if possible.|