Network Management
Server Health dashboard shows “No Data for Selected Time Period” or missing nodes in NPM 2024.4
In NPM 2024.4, a node that was previously visible on the Server Health dashboard can disappear and the Server Health view may show “No Data for Selected Time Period” even though the node is still being monitored. This is typically caused by non-obvious configuration changes (stats collection flags, polling method, or Server Health resource filters) rather than a core product defect.
First published date
Last published date
Overview
A Windows server node was previously visible on the SolarWinds Server Health Check dashboard but no longer appears in the Server Health resources.
At the same time, the Server Health view shows “No Data for Selected Time Period” for the node’s CPU/Memory widgets, suggesting that monitoring data is not being displayed for the selected interval.
The node is still present in the SolarWinds Platform and may have other data, but Server Health either cannot find recent CPU/memory statistics or is filtering the node out of the resource scope.
Product section
Cause
Most commonly one (or more) of the following configuration issues:
-
Statistics collection disabled for the node
- In List Resources, the option “Collect statistics for CPU, memory, and volumes” is unchecked for the node.
- Result: No CPU/memory rows are written to the database → Server Health charts return no data.
-
Polling method set to “Status only”
- The node’s polling method is changed to Status only instead of Agent/WMI/SNMP.
- Result: Only status is polled; performance metrics (CPU/Memory) are not collected.
-
Server Health resource filters excluding the node
- The Server Health CPU/Memory resources are filtered to a group, custom property, or SWQL/SQL condition the node no longer matches (for example, a “SolarWinds servers only” group or a custom property that was changed).
- Result: The node has data, but is filtered out of the Server Health widgets.
-
Time-range mismatch or resource corruption (less common)
- The selected time period does not overlap with when data was collected, or the Server Health resources on the view are corrupted and must be recreated.
Resolution
-
Check node-level CPU/Memory charts
- Open Node Details for the affected node.
- Review CPU Load and Average Memory Used charts for the same time range.
- If these charts also show “No data for selected time period”, continue with Steps 2–3 (collection issue).
- If node charts show data but Server Health does not, skip to Step 4 (filters/resources).
-
Verify statistics collection is enabled
- On the node, click List Resources.
- Ensure “Collect statistics for CPU, memory, and volumes” is checked.
- Click Submit, then wait a few polling cycles and re-check the node’s CPU/Memory charts and the Server Health view.
-
Verify polling method is not “Status only”
- Edit Node Properties for the affected node.
- Confirm the polling method is Agent, WMI, or SNMP (depending on environment), not Status only.
- Save changes and allow several polling cycles, then verify that node CPU/Memory charts and Server Health begin to populate.
-
Review Server Health view filters
- Go to the SolarWinds Server Health page.
- Click EDIT on the SolarWinds Memory usages and SolarWinds CPU usages resources.
- Under View Options / Filter:
- Confirm the resources are not limited to a group or custom property the node no longer matches.
- Temporarily remove any custom filters (SWQL/SQL or custom property filters).
- Set the time period to a broad range such as Last 24 Hours.
- Apply changes and check whether the missing node appears.
- If it does, add filters back one by one to identify which group/custom property condition was excluding the node.
-
Recreate Server Health resources (if charts still show no data)
- On the Server Health page, delete the SolarWinds Memory usages and SolarWinds CPU usages resources from the view.
- Add them back from the out-of-the-box resource list for that view type.
- This refreshes the resource definition in case it has become corrupted.
- Re-apply any required filters carefully, testing that the affected node still appears.