Submit a ticketCall us

WebinarWebinar: A checklist for planning your Network Performance Monitor (NPM) upgrade

Are you ready for your next upgrade? To help you plan smoothly, join this webcast to learn more about, SolarWinds® Orion® Installer, SolarWinds Upgrade Advisor, Upgrades Guides, Training Videos, and other resources available. We’ll share key upgrade planning considerations, lessons learned from customers with practical advice from SolarWinds Product Experts. We’ll also give practical tips to identify the estimated time needed and resources, how to prepare the business and IT staff for changes, ways to plan for required system changes, and more.

Register now.

Home > Success Center > Network Performance Monitor (NPM) > NPM - Knowledgebase Articles > Alternative for the Node Availability Resource

Alternative for the Node Availability Resource


This article explains an alternative solution for the Node Availability resource in cases when it times out or takes a long time to load.


All NPM versions


The nodes availability resource could take a long time to load the page. This is usually caused by volume of statistics to load on all nodes or the SQL is not performing as it should.

Helpful Alternative

  1. Create a custom table resource on any page. 
  2. Select Data Source.
  3. Click Selection Method: Advanced DataBase Query (SQL, SWQL).
  4. Modify the query to include any type of Group by selectors such as a custom property. See the following example below:
    Note: SolarWinds Support cannot help modify this query to include a group by your choice:

ROUND(SUM((CASE WHEN [data].[ResponseTimeHistory].[Availability] < 0 THEN NULL ELSE [data].[ResponseTimeHistory].[Availability] END)*(data.ResponseTimeHistory.Weight))/SUM(case when ((CASE WHEN [data].[ResponseTimeHistory].[Availability] < 0 THEN NULL ELSE [data].[ResponseTimeHistory].[Availability] END) is null) then 0 else (data.ResponseTimeHistory.Weight) end),3) AS [Last 30 Days] 
FROM Orion.Nodes AS data 
WHERE NodeID = ${NodeID} 
AND ToString(DayDiff(ToLocal([data].[ResponseTimeHistory].DateTime),GETDATE())) <= 30 


If the issue is in Custom Query resources, SolarWinds recommends to include paging capability. And this takes first column and it wasn't parsed well. 

If the paging scalability is not the first column, add some dummy column as the first column in query, which will simulate paging.

SELECT '${Caption}' as Caption,

Last modified