How SolarWinds Platform calculates availability based on Polling results stored in Database.

2/23/2022 3:20 PM

11/13/2025 12:43 AM

This is how the availability of Node is calculated in NPM

Network Performance Monitor

By default, We poll every 120 seconds, 

• if no reply STATUS = WARNING, and Fast Polling occurs every 10s for 120 seconds.
• If still no reply after those 12 polls STATUS = DOWN. See Node warning levels for more.

For more information, see “Managing Packet Loss Reporting”.

To set the Node Warning Level: 

• 1.             Log in to the SolarWinds Platform Web Console using an account with administrative rights.
• 2.             Click Settings in the upper right of the web console, and then click Polling Settings in the Settings group of the Orion Website Administration view.
• 3.             In the Calculations and Thresholds group, set the Node Warning Level to an appropriate interval, in seconds.  Note: The default Node Warning Level interval is 120 seconds.
• 4.             Click Submit.

The Availability Calculation tab allows you to select one of two methods for determining device availability. 
This can be Set on the Web Admin Settings page.

• Web -> Settings -> Polling Settings
• 

To See actually data behind availability, pick an example Node's NodeIDs and use following SQL Query:

• SELECT TOP 10000 * FROM [dbo].[ResponseTime]
  where nodeid =2
  
  order by datetime desc
  
  -- Scripts are not supported under any SolarWinds support program or service.
  -- Scripts are provided AS IS without warranty of any kind. SolarWinds further
  -- disclaims all warranties including, without limitation, any implied warranties
  -- of merchantability or of fitness for a particular purpose. The risk arising
  -- out of the use or performance of the scripts and documentation stays with you.
  -- In no event shall SolarWinds or anyone else involved in the creation,
  -- production, or delivery of the scripts be liable for any damages whatsoever
  -- (including, without limitation, damages for loss of business profits, business
  -- interruption, loss of business information, or other pecuniary loss) arising
  -- out of the use of or inability to use the scripts or documentation.
  

Method 1:

The default method is based upon the up or down status of the node. 
As long as the device responds to a ping within the default two-minute warning interval, the node is considered up.

Availability calculations are based purely on the response of the device. 
If it responds we log that as 100% available if it does not respond then we log that as 0% available. 
Latency is not factored into the calculations. 

 These calculations are only based on the records that exist, 
so if a server came online mid-month availability will be only factored for the time the node existed in SolarWinds Platform. 
For scheduled outages, provided the node was put into an Unmanaged state, 
we would exclude that time since no records will exist for that time period.

We take the data from the response time table for availability for the number of records 
that correlate to the time period you want to see availability calculated for, 
and then take the average of all of those data points. 
The data for availability is recorded as 100% available or 0% unavailable.
 

Method 2

                Bases the determination of node availability on a packet loss percentage.
 

*********************************************************************************************************************************
SolarWinds Platform Web Console -> Settings -> Polling Settings -> Availability Calculation (advanced)
Calculations & Thresholds

 

Availability Calculation (advanced)

Node status is recommended. Availability is based on the up or down status of the node.

SWNetPerfMon-Settings-Availability Calculation
1 for Node Status.
2 for Percent Packet Loss.