Documentation forServer & Application Monitor
Monitoring your applications and environment is a key capability of Hybrid Cloud Observability and is also available in a standalone module, Server & Application Monitor (SAM). Hybrid Cloud Observability and SAM are built on the self-hosted SolarWinds Platform.

Skype for Business Server 2015 (Edge Role)

This template assesses the status and overall health of services as well as the performance of the Microsoft Skype for Business Server (Edge Role) 2015.

Prerequisites

WMI access to the SharePoint server. You can also use the SolarWinds Platform agent for Windows with this template.

Credentials

Windows Administrator on the SharePoint server.

Set thresholds for these counters according to your environment. SolarWinds recommends monitoring counters for some period of time to understand potential value ranges and then set the thresholds accordingly.

Component monitors

Click here for an overview about SAM application monitor templates and component monitors. SAM API Poller templates are also available.

Components without predetermined threshold values provide guidance such as "Use the lowest threshold possible" or "Use the highest threshold possible" to help you find a threshold appropriate for your application.

Skype for Business Server Replica Replicator Agent

This component monitor returns the CPU and memory usage of the Skype for Business Server Replica Replicator Agent. This service is used by the File Transfer Agent for replication configuration settings.

SIP - Incoming Requests /Sec

This component monitor returns the rate of received requests, per second. You will need to baseline this counter by testing and monitoring the user load.

SIP - Incoming Messages /Sec

This component monitor returns the rate of received messages, per second. You will need to baseline this counter by testing and monitoring the user load.

SIP Peers: Connections Active

This component monitor returns the number of established connections that are currently active. A connection is considered established when peer credentials are verified (e.g. via MTLS), or the peer receives a 2xx response. You will need to baseline this counter by testing and monitoring the user load. This returned value should be less than 15,000 connections per Front-End.

SIP Peers: Average Outgoing Queue Delay

This component monitor returns the average time, in seconds, that messages have been delayed in outgoing queues. Check the Outgoing Queue Delay for delays in sending messages to other servers or clients that could be causing messages to be accumulated in the server. The server will drop client connections if it is in a throttle state and messages stay in the outgoing queue for more than 32 seconds.

SIP Peers: Connections Active

This component monitor returns the average time that the server held the incoming messages currently being processed. This should usually be less than one second, on average, but it is normal to see short spikes of up to three seconds. The server will throttle new incoming messages after going above the high benchmark and until the number of messages falls below the low benchmark. The server starts rejecting new connections when the average holding time is greater than overload time of 15 seconds.

This template also includes multiple A/V Edge UDP component monitors. For details, edit the template and expand each monitor to display its description.