This article provides a detailed listing of Lync 2013/Skype for Business 2015 Front End Key Health Indicators from Microsoft, as well as an attachment with a full listing of other key health indicators.
Follow this article to understand what is the healthy range for Lync 2013/Skype for Business 2015 key Front End Health Indicators.
Lync Server 2013 | Skype for Business Server 2015
How it Works
Lync 2013/Skype for Business 2015 has many Health Indicators that can give you an overview of the overall health of the environment.
The attached Excel file from Microsoft contains a full list of the Lync Server 2013/Skype for Business 2015 Key Health Indicators; with descriptions of the indicators and their Healthy Range.
It provides information for the following components:
- Front End
- SQL
- MCUs
- Web Components
- Conferencing
- Mediation
- Mobile
- Edge
Below is a view of the Front End Health Indicators from the list:
| FRONT END HEALTH: Monitor on all Front End Servers | |||
| Counter | Description | Healthy Range | |
| \LS:Usrv - DBStore\Usrv - Queue Latency (msec) | The average time a request is held in the request queue to RTCDyn database | < 100ms sustained | |
| \LS:Usrv - DBStore\Usrv - Sproc Latency (msec) | The average time it takes to execute a sproc call against RTCDyn database. | < 100ms sustained | |
| \LS:Usrv - DBStore\Usrv - Throttled requests/sec | The number of requests that were rejected with a retry since the database queue latency was high. | 0 | |
| \LS:Usrv - REGDBStore\Usrv - Queue Latency (msec) | The average time a request is held in the request queue to RTC database | < 100ms sustained | |
| \LS:Usrv - REGDBStore\Usrv - Sproc Latency (msec) | The average time it takes to execute a sproc call against RTC database. | < 100ms sustained | |
| \LS:Usrv - REGDBStore\Usrv - Throttled requests/sec | The number of requests that were rejected with a retry since the database queue latency was high. | 0 | |
| \LS:Usrv - SharedDBStore\Usrv - Queue Latency (msec) | The average time a request is held in the request queue to RTCShared database | < 100ms sustained | |
| \LS:Usrv - SharedDBStore\Usrv - Sproc Latency (msec) | The average time it takes to execute a sproc call against RTCShared database. | < 100ms sustained | |
| \LS:Usrv - SharedDBStore\Usrv - Throttled requests/sec | The number of requests that were rejected with a retry since the database queue latency was high. | 0 | |
| \LS:SIP - Authentication\SIP - Authentication System Errors/sec | The per-second rate of authentication failures caused by system errors (due to low memory conditions or otherwise). | < 1 | |
| \LS:SIP - Load Management\SIP - Average Holding Time For Incoming Messages | The average time that the server held the incoming messages currently being processed. | < 1 | |
| \LS:SIP - Load Management\SIP - Incoming Messages Timed out | The number of incoming messages currently being held by the server for processing for more than the maximum tracking interval. | < 2 | |
| \LS:SIP - Peers(*)\SIP - Average outgoing Queue Delay | Average outgoing queue delay in seconds | < 2 | |
| \LS:SIP - Peers(*)\SIP - Flow-controlled Connections | The number of connections that are currently being flow-controlled (no socket receives are posted) | < 2 | |
| \LS:SIP - Peers(*)\SIP - Sends Timed-Out/sec | The total number of sends dropped because they stayed in the outgoing (send) queue for too long. | 0 | |
| \LS:SIP - Protocol\SIP - Average Incoming Message Processing Time | The average time (in seconds) it takes to process an incoming message. | < 1 | |
| \LS:SIP - Protocol\SIP - Incoming Requests Dropped/sec | The per-second rate of incoming requests dropped because they could not be processed (due to bad headers, insufficient routing information, server resource allocation failure). | < 1 | |
| \LS:SIP - Protocol\SIP - Incoming Responses Dropped/sec | The per-second rate of incoming responses dropped because they could not be processed (due to bad headers, insufficient routing information, server resource allocation failure). | < 1 | |
| \LS:SIP - Responses\SIP - Local 503 Responses/sec | The total number of 503 responses generated by the server per second | 0 | |
| \LS:RoutingApps - Inter Cluster Routing\RoutingApps - Number of primary registrar timeouts | Number of requests for which backup registrar timed out | 0 | |
| \LS:RoutingApps - Inter Cluster Routing\RoutingApps - Number of backup registrar timeouts | Number of requests for which backup registrar timed out | 0 | |
| \LS:LYSS - Storage Service API\LYSS - Current percentage of space used by Storage Service DB. | Current percentage of space used by Storage Service DB. | < 80 | |
| \LS:LYSS - Storage Service API\LYSS - Current number of Storage Service stale queue items | Current number of Storage Service queue items which are not owned and last attempted a long time ago. | 0 | |
| \LS:Usrv - Cluster Manager\Usrv - Number of data loss events with state change | Total number of data loss events with state change | 0 | |
| \LS:Usrv - Cluster Manager\Usrv - Number of data loss events without state change | Total number of data loss events without state change | 0 | |
| \LS:Usrv - Cluster Manager\Usrv - Number of failures of replication operations sent to other Replicas per second | The per-second rate of replication operation failures | 0 | |
| \LS:Usrv - Cluster Manager\Usrv - Wheather server is connected to fabric pool manager | Indicates whether server is connected to fabric pool manager. | 0 | |
| \LS:XMPPFederation - SIP Instant Messaging\XMPPFederation - Failure IMDNs sent/sec | Failure IMDNs sent/sec | 0 | |
| \LS:RoutingApps - Emergency Call Routing\RoutingApps - Number of incoming failure responses | Number of times an Emergency Call failure response was received from Gateway. | 0 |