Lync Monitoring Server Summary (Clifs Notes)
The purpose of this post is to help identify the requirements to monitor your Lync Implementation holistically. Real-Time montioring happens within the (optional) OpsMgr Managment Pack, and detailed reporting happens within the Lync Monitoring Server and the Reports deployed along with the Lync Monitoring Server Role. In order to monitor your Lync Implementation fully, it is suggested to use both OpsMgr and the Lync Monitoring Server.
The Lync Monitoring Server simplifies the ability to gather data about the quality of your network media, in both Voice calls and A/V conferences. The Monitoring Server also collects call error records (CERs), which you can use to troubleshoot failed calls. The Monitoring Server collects usage material in the form of call detail records (CDRs) about various Lync Server components so that you can analyze ROI and plan the capacity requirements of the Lync implementation. A single Monitoring Server is able to support up to 250,000 users if not collocated with an Archiving Server. If collocated, the Monitoring Server is able to support up to 100,000 users. Reporting is provided out of the box, but may not provide a holistic view of the entire platform the Lync Environment is deployed upon (SQL, IIS, OS).
o System file and Message Queuing file on the same physical disko QoE database data file and CDR database data file on the same physical disko QoE database log fileo CDR database log file
o The CDR database grows 31.5 KB per user per dayo The QoE database grows 28 KB per user per day
o For example, 60 days of data in the CDR database for 50,000 users would be 31.5*50000*60 for a total of 90 GB. If your organization’s Lync Server differs significantly from the user model, adjust the daily database growth estimate.