Observability

Node Status widget does not match Node List when filtering by custom properties in Modern Dashboards in SolarWinds Platform

This article provides information about a SolarWinds Platform issue where the Node Status (KPI) widget on a Modern Dashboard does not honor filters based on node custom properties, while the Node List widget on the same dashboard does. As a result, the Node Status counts can be misleading when dashboards are filtered by node custom properties.

First published date

3/27/2026 10:22 PM

Last published date

6/9/2026 4:15 PM

Overview

In SolarWinds Platform 2026.1, Modern Dashboards can be configured with:

  • A Node List widget (standard Nodes list, no custom SWQL), and
  • A Node Status widget (built-in KPI / proportional “Node Status” widget, no custom SWQL),
  • A filter with Entity type = Orion.Nodes, including custom properties as filterable fields.

When a user applies a filter based on a node custom property, the following behavior is observed:

  • The Node List widget correctly shows only the nodes that match the custom-property filter (for example, Region = EMEA, Environment = Production, or Owner = TeamA).
  • The Node Status widget continues to show counts (Up / Warning / Critical / Down / Unmanaged / Other) as if the filter were not applied, or as if the widget were scoped to a different/unfiltered set of nodes.

No explicit error is displayed in the web console. From the user’s perspective, the dashboard renders normally, but the numerical values in the Node Status tiles do not align with the filtered Node List.

Example of observed behavior (values are illustrative):

  • Global filter: CustomProperty_Region = Region01
  • Node List: shows 10 nodes (all in Region01).
  • Node Status: shows Up = 5000, Warning = 100, Critical = 50, etc. — clearly reflecting the entire environment, not just the 10 filtered nodes.

If the same filter is changed to a non-custom-property field such as Caption = NODE-001, both widgets behave correctly and their results match.

Product section

Hybrid Cloud Observability

Cause

This is a known product defect in the Modern Dashboards implementation:

  • The Node List widget correctly applies global Orion.Nodes filters, including filters on node custom properties.
  • The Node Status KPI widget currently does not apply the custom-property portion of the filter, and instead calculates its counts on a broader node set (typically the full environment or a differently scoped set).

In other words, custom-property–based filters are not wired through to the Node Status widget’s underlying query, while they are correctly wired for the Node List widget.

Resolution

This issue is addressed in SolarWinds Platform 2026.2. Consider upgrading your environment.