As I mentioned the other day, I previously did a post on Monitoring Server for Lync 2010:
What Monitoring Server Monitors – and What It Doesn’t
With Lync Server 2013, a few things have changed.
Now you can home the Monitoring Server Role on your Front End Server. It doesn’t require a separate server anymore. Neither does its sibling service, Archiving.
I think this actually makes monitoring easier, both to set up and to retrieve information. The number and depth of Monitoring Reports were also increased for 2013:
- New reports on voice quality: Media Quality Comparison Report (compares quality between different kinds of calls), Conference Join Time Report (gives information on the time it takes users to join a conference).
- More details on video and application sharing. Now the Media Quality Summary Report has information on video calls and calls where you share apps. If there’s a problem with these call types, the Server Performance Report can help you pinpoint which server has the problem.
Speed of report generation & retrieval has gone up too. No big surprise, since it’s homed on the Front End Server.
With new reports and expanded current ones, does Monitoring Server have a farther reach than its 2010 predecessor? Does it monitor things Lync Server 2010 didn’t?
What Monitoring Server (Lync 2013 Version) Monitors
- Usage information on all communication sessions. VoIP calls, conferencing, and IM.
- Peer-to-Peer session information. Any two users communicating in any Lync medium (including application sharing and video, as I mentioned above).
- Any failures in communication sessions (logged per user and in aggregate), including which failures occurred most frequently and where the failures originated.
- Response Group Usage data.
- Lists and data of Call Admission Control-restricted activities.
- Metrics on call quality, signaling issues such as jitter, location data and devices used by Lync Server.
- Details on calls made and received.
Pretty much everything it monitored before, plus some new reports on voice quality and expanded reporting for more developed services in 2013, like video calls and sharing.
Still, it doesn’t cover everything.
What Monitoring Server (2013 Version) DOES NOT Monitor
- Since Archiving Server is still around, it’s responsible for contents of IM sessions, conferences, whiteboards and phone calls. Not Monitoring Server.
- Monitoring for the Windows Servers on which Lync is installed. Sorry, it still doesn’t cover the Windows Server! Make sure to install a server monitoring tool.
- Non-Lync Server application logging. If you have other services homed on the same server (which I don’t recommend!), Monitoring Server will not report on them.
Monitoring in Lync Server 2013 covers everything its 2010 predecessor does–as well as the new capabilities introduced in 2013. It does remain Lync-specific though. Which is good; focusing on the complexities of Lync processes means we have plenty of data for support and growth.
One thing to note: If you use the Monitoring Dashboard to keep track of Lync Server activity, remember that it only displays reports going back 6 months. Reports are NOT deleted after 6 months – they just aren’t shown in the Dashboard. Refer to specific reports if you need data older than that.
That’s it for 2013! We’re taking off for the next 2 weeks. PlanetMagpie wishes all our Lync Insider readers a Merry Christmas and Happy Holidays.
I’ll see you all back here the week of January 6th, for a fresh start in 2014. Take care!