Submit a ticketCall us

Bridging the ITSM Divide
Integrated help desk and remote support software for faster resolution

Join us on Wednesday, November 29, 2017 at 11 a.m. CT, as we discuss the benefits of effectively integrating your help desk software with remote support solutions to help increase the efficiency of IT administration, improve communication, and decrease mean time to resolution (MTTR) for IT issues of all sizes. This directly impacts end-user satisfaction and your business’ bottom line. Register 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: 7 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