Submit a ticketCall us

Get a crash course on Network Monitoring delivered right to your inbox
This free 7-day email course provides a primer to the philosophy, theory, and fundamental concepts involved in IT monitoring. Lessons will explain not only how to perform various monitoring tasks, but why and when you should use them. Sign up now.

Home > Success Center > Network Performance Monitor (NPM) > 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 Karen Valdellon on Jul 11, 2016

Views: 5 Votes: 0 Revisions: 2

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
21:37, 10 Jul 2016