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

Impact of modifying "All Nodes" resource

bfaltys

I've just recently starting working with NPM again after a couple years without touching it so bear with me. One item I've been looking at is what will happen if I edit the All Nodes resource under a view. Specifically, if I change how the nodes are listed, will it only be for that view or will any view using the All Nodes resource also be changed? If it will change for all views using that resource, is there a way to make a custom sort of All Nodes resource that could be used just for this view? I was able to make a table, but that didn't look as nice and also was fully expanded and took up a lot of space.

Find more posts tagged with

Accepted answers

janene16

yes, editing a resource from a default view is a global thing. how about just create a new view (or you can also copy the existing view), then add/edit the All nodes resource?

once done, you can assign that copied view to whoever you think wanted to have the customized All Nodes resource

All comments

janene16

yes, editing a resource from a default view is a global thing. how about just create a new view (or you can also copy the existing view), then add/edit the All nodes resource?

once done, you can assign that copied view to whoever you think wanted to have the customized All Nodes resource

bfaltys

My plan is to create a new view that contains the All Nodes resource. From there I only want to show a subset of nodes and I want to display/organize them differently than other views. I just wanted to make sure that if I customize how they're displayed it won't impact other views.

jblankjblank

bfaltys - you have a couple of ways in which you can do this. If you are customizing a resource under a particular view, it won't impact other views, but it could impact other accounts or users that have access to that view. You can create a view and then customize accounts to have particular limitations so that when a user with a customized account logs in, they see only the entities you wish. Or you can create customized views, and then grant accounts access to that specific view.

The SWQL filter at the bottom of the resource can be of benefit, especially if you are utilizing custom properties. I assume the subsets of nodes have some sort of distinction between them, so make that the custom property. Then set the filter for that property. You can do the same with many of the resources in Orion.

Other resources such as the Custom Summary Tile have built in filters as well. This will carve out the entities chosen, then break them out per status. Clicking on the status for the 2 down nodes in the below example will bring up a list of the nodes impacted.