Response time is the amount of time it takes for a service request to return a response. It is a critical

SLA performance metric for a hosted data center service, as it directly affects the user experience

and satisfaction. High response time can indicate network congestion, server overload, or other

performance issues that can degrade the quality of the service. By tracking response time, you can

monitor the availability and reliability of the service, identify and troubleshoot potential problems,

and ensure that the service meets the SLA expectations and standards. Reference: How to measure

your SLA: 5 Metrics you should be Monitoring and Reporting, Data Center SLA Frequently Offer a

100% Uptime Guarantee, How To Measure SLA Performance in 4 Steps (With Tips).

Capacity usage trends are calculated based on historical data. By default, the longest time period

taken into account for calculating the capacity forecast is 180 days. The more historical data up to 180

days are available, the more precise is the calculated forecast. Forecast calculation methods include

peak calculation and average calculation, which can be set globally or customized for individual

objects. Capacity forecasting is available for nodes, interfaces, and volumes that meet certain

requirements, such as being managed in NPM and having enough historical data in the

database. Reference: Monitor capacity usage trends on the network and forecast capacity issues in

NPM, Forecast capacity for nodes, interfaces, or volumes in NPM, Real-Time Network Monitoring

Tool

By default, NPM uses the global critical CPU threshold for node statuses, which is 90%. However, you

can override this threshold for individual nodes by editing their properties and specifying a custom

value for the critical CPU threshold. This way, you can adjust the threshold according to the specific

characteristics and performance of each node. Changing the critical CPU threshold on the node will

affect how the node status is calculated and displayed in the web console, as well as how the alerts

are triggered based on the CPU utilization. Reference: Thresholds in the SolarWinds Platform; CPU

Critical Threshold - Forum - Network Performance Monitor (NPM) - THWACK

Device Studio is a feature in the SolarWinds Platform Web Console that allows you to create custom

pollers for devices or technologies that are not supported by default in NPM. You can use Device

Studio to create pollers for CPU and memory, as well as other metrics, by defining the object

identifiers (OIDs) and formulas that you want to poll. Device Studio currently supports SNMP and

WMI polling technologies, and you can test, assign, and edit your custom pollers from the Manage

Pollers page. Reference: Create pollers in Device Studio for NPM, Device Studio, Device Studio Poller.

The Universal Device Poller (UnDP) is a feature that allows users to create custom monitors for

almost any statistic provided by SNMP based on its Management Information Base (MIB) and object

identifier (OID). However, sometimes the OID that the user wants to monitor may not be available in

the MIB tree, either because it is not supported by the device or because the MIB database is

outdated. In this case, the user needs to update the MIB database to get the latest MIBs from the

SolarWinds website or from the device vendor. This will ensure that the UnDP can find the OID in the

MIB tree and poll it successfully12. Reference: 1: Update the SolarWinds MIB Database for the

SolarWinds Platform3, 2: Monitor custom statistics based on OIDs with Universal Device Pollers in

the SolarWinds Platform

https://documentation.solarwinds.com/en/success_center/orionplatform/content/coredownloading-the-solarwinds-mib-database-sw3581.htm