Submit a ticketCall us

Solarwinds & Cisco Live! Barcelona
Join us from the 29th of January to the 2nd of February at Cisco Live 2018 in Barcelona, where we will continue to show how monitoring the network with SolarWinds will keep you ahead of the game. At our booth (WEP 1A), we will demonstrate how SolarWinds network solutions can help. As a bonus, we are also hosting a pre-event webinar - Blame the Network, Hybrid IT Edition with our SolarWinds Head Geek™, Patrick Hubbard on January 24th - GMT (UTC+0): 10:00 a.m. to 11:00 a.m. There's still time to RSVP.

Home > Success Center > Network Performance Monitor (NPM) > 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