nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Community
- Command Central
- MVP Program
- Monthly Mission
- Blogs
- Groups
- Events
- Media Vault
Products
- Observability
- Network Management
- Application Management
- IT Security
- IT Service Management
- System Management
- Database Management
Content Exchange
- SolarWinds Platform
- Server & Application Monitor
- Database Performance Analyzer
- Server Configuration Monitor
- Network Performance Monitor
- Network Configuration Manager
- SQL Sentry
- Web Help Desk
Free Tools & Trials
Store

Orion 9.1 Ajax all nodes tree

aLTeReGo

I just upgraded to Orion 9.1 on my production server and I'm noticing in my All Nodes Ajax tree that if there's a node configured as "unmanaged", the root status shows "unknown" gray. Is this a bug or should I open support ticket?

NodeStatus.png

Find more posts tagged with

Accepted answers

All comments

FormerMember

It's a bug. We'll get it fixed. Unmanaged should be ignored on rollup.

SamuelB

Another bug has popped up in this version of the all nodes tree. If the node list is being grouped by 3 custom properties and one of them is "Null" then the resource is putting the node in an "Unknown" group. Previously, the resource would ignore the "Null" value and just drop the node in the group above instead of an "Unknown" group. This is similar to the problem from an earlier version of Orion that is discussed in this post: .

FormerMember

Another bug has popped up in this version of the all nodes tree. If the node list is being grouped by 3 custom properties and one of them is "Null" then the resource is putting the node in an "Unknown" group. Previously, the resource would ignore the "Null" value and just drop the node in the group above instead of an "Unknown" group. This is similar to the problem from an earlier version of Orion that is discussed in this post

Thanks. That bug will be fixed in SP1.

tdanner

I've seen people advocating for both behaviors (nulls go in the Unknown group and nulls go "loose"), so I think I'll just make it configurable by clicking Edit on the resource.