Submit a ticketCall us

Have You Auto Renewed? If not, you're missing out.
The SolarWinds Renewal Program comes with a host of benefits including the most recent product updates, 24/7 technical support, virtual instructor-led training and more. Experience all of this with the convenience of Auto Renewal, and never worry about missing any of these great benefits. Learn More.

Home > Success Center > Archive > 2017December18 - Deletes > VMAN objects not filtered by node-based limitations

VMAN objects not filtered by node-based limitations

Table of contents
Created by Robert Stidman, last modified by Kevin.Swinson on Dec 18, 2017

Views: 519 Votes: 0 Revisions: 3

Updated July 11, 2016


This article explains why VMAN objects do not appear to be filtered by the view limitation.


Any Orion with VMAN but specifically seen with NPM v12


VMAN objects do not use node custom properties. In some cases, a view limitation may be applied to nodes. For example, via a node custom property. Confusion may occur because those same nodes may also be separate objects in VMAN, and the events will show them only by name, not differentiating the object type on the surface. In that, way it will appear that the objects are not being filtered by the view limitation when they, in fact, do not apply to it at all.




Last modified