Submit a ticketCall us

WebinarUpcoming Webinar: Know What’s Changed – with NEW Server Configuration Monitor

Change management in IT is critical. But, even with a good change management process, changes are too often not correctly tracked, if at all. The configuration of your servers and applications is a key factor in their performance, availability, and security. Many incidents can be tracked back to an authorized (and sometimes unauthorized) configuration change, whether to a system file, configuration file, or Windows® Registry entry. Join SolarWinds VP of product management Brandon Shopp to discover how the new SolarWinds® Server Configuration Monitor is designed to help you.

Register now.

Home > Success Center > Network Performance Monitor (NPM) > SQL filter is not working in Resources when using NodeId

SQL filter is not working in Resources when using NodeId

Table of contents
No headers
Created by Interspire Import, last modified by MindTouch on Jun 23, 2016

Views: 1,630 Votes: 0 Revisions: 7

The database structure has changed in NPM v11.5. When using custom SQL filters working with Nodes table, the references to the NodeId should be updated to NodesData.NodeId.
NodesData.NodeId<10 is ok.
NodeId<10, it will stop working for NPM v11.5 and other Core 2015.1 products.

Applies to: NPM v11.5 and Core 2015.1 products 

Last modified

Tags

Classifications

Public