If you haven’t read about or used the Lync performance monitor counters, or maybe didn’t even realize they were there, This post if for you. With all the research I did on Centralized logging, I came across a medium of collecting Data collector sets. I’m not sure what that sentence even means, but I’m too tired to worry about it. So moving right along. Here is the basics, of which I have not yet mastered, but nevertheless, will refer back to this some time of need:
Fist the learning curve. How do I start? Basic. The Lync Counters are loaded when you installed the product. so use the LMS to get a list:
- Get-Counter -ListSet * | fl CounterSetName
- Get-Counter -ListSet “LS:*”
- Get-Counter -ListSet “LS:*” | Select-Object CounterSetName, Description | Format-List
The last one is handy because you can add the MCU (CounterSetName) and get a list against the different workloads.(44). See figure 1:
Either of these spits out a lovely list of counters that is very confusing to stare at. However, good information it is. I also recently watched a Video on performance topics, which identifies a good list of counters, which really pulls allot of red flags out of the the large number of possibilities, yielding a very nice voice conferencing set to work with
Figure 1. (CounterSetName)
The man’s name is Bill Nyce and the Video is called OPER300_Nyce. I will put my counter list at the bottom of this post, or you my find the video and Power Point from the site, lyncconf.com. We are thankful the information was made publicly available. There is so much good material here.
So having the CounterSet name, we can use it to get a specific detail counter. Lets say we have a call failing. choosing from the list, Sip and SipEps seem like good choices. So I filter on those names. The star is key or the search wont work:
- Get-Counter -ListSet “LS:Sip*” | Select-Object CounterSetName, Description | Format-List
This list returns the set names for SIP. I am choosing Sip – Requests, running the same command with more detail this time, for example:
- Get-Counter -ListSet “LS:Sip – Requests*” | Select-Object CounterSetName, Description | Format-List
- Get-Counter -ListSet “LS:Sip – Requests*” | Select-Object –ExpandProperty Counter| Format-List
I have formed the shell command correctly, but the results don’t seem useful:
So I try “SipEps and this looks much more interesting:
- Get-Counter -ListSet “LS:SipEps – SipEps Incoming Messages” | Select-Object CounterSetName, Description | Format-List
- Get-Counter -ListSet “LS:SipEps – SipEps Incoming Messages” | Select-Object –ExpandProperty Counter| Format-List
The bottom line is this can be very useful on the command line. However, the most value may be in the data collector set. A data collector Uses the Windows Performance Monitor:
Under properties, you can add your Lync counters. Or you can import a template from the share located SkyDrive. The file is called LyncDataCollect.xml. To add your collector, right click under data collector set (the user defined folder). Choose Create from template.
Select “basic” and then browse to the XML file. Alternatively you can choose any counters you like. All of the Lync counter categories are all “LS”. Once selected, you can finish and customize the collector to run and stop as you wish. The reporting gives a nice graphical report of possible trouble with a voice Deployment.
I found that the next hop blog has done a way better job at this then I ever could. Some references in this article are from concepts brought to me by reading the MS blog LYNC pages. Also, the counter information was collected from the Lync Conference 2013 in San Diego.