On Sunday, I received an email from a UK consulting firm. The individual (I’ll call him Mr. B) wanted to know about monitoring Lync Server.
Now, his question was more about identifying the signs of a well-functioning Lync setup. But it touched off a related question in my mind – how much monitoring does Lync Server do for itself?
Turns out, quite a lot. Lync’s Monitoring Server role keeps tabs on just about every communication in & out. It’s not a required server role for Lync to run, but it’s recommended.
Why? Simple reason – Monitoring Server reports help you figure out what’s working (and what’s not).
Reports are broken down into four categories: System Usage Reports, Call Diagnostic Reports, Call Diagnostic Reports (per user), and Media Quality Diagnostic Reports. Makes it easier to identify a specific problem, if you know what type of problem you’re looking at.
What Monitoring Server DOES Provide
Overall, reports cover pretty much everything you’d want to know about how good a job your Lync Server’s doing. For example, you can find all of this in Monitoring Server reports:
- Information about the communication sessions in your organization. That covers VoIP phone calls, IM sessions and conferences.
- Endpoint information about each session. IP addresses, connection speeds, which Edge Servers were used, etc.
- Quality measurements for the different types of communications you use (SIP calls, video conferencing, etc.).
- Activity lists for each user in the organization, by date and/or session type.
- Reports on Call Admission Control-restricted sessions.
- Summary of (and details on) calls made to Response Group workflows.
- Diagnostic reports and troubleshooting information for session failures (including SIP response codes and diagnostic headers).
- Server Performance reports: Shows you which servers have had the most problems, using metrics like packet loss, signal degradation, noise, etc.
And a few more.
Many of the Monitoring Server reports are broken up by type, or medium. For example, one report will tell you about IM sessions, broken down by pool. Another will tell you about VoIP calls in the same pool. A third could provide a summary of all communications in that pool.
What Monitoring Server DOES NOT Provide
- The content of a phone call, IM session or conference. That’s the job of Archiving Server.
- Monitoring for the Windows Servers Lync is installed on. It doesn’t cover Windows processes. Use a standard server monitoring tool for that.
- Non-Lync Server application logging. Use a third-party tracking tool to track activity on these.
Microsoft has a Work Smart guide for Monitoring Server here: Lync Server 2010 Monitoring Server Reports Work Smart Guide – Microsoft Download Center
Plenty of information on each report, what it records, and how to make use of the data.
Have you referred to a Monitoring Server report lately? What did you find out?