Submit a ticketCall us

Training ClassThe Orion® Platform Instructor-led Classes

Provided by SolarWinds® Academy, these trainings will introduce users to the Orion Platform and its features, management, and navigation. These courses are suitable for users looking to discover new tips, tricks, and ways to adapt their Orion products to better suit their monitoring needs:
Deploying the Orion Platform
Configuring Orion views, maps, and accounts
Configuring Orion alerts and reports

Reserve your seat.

Home > Success Center > Network Performance Monitor (NPM) > NPM - Knowledgebase Articles > NPM 12 bug: Custom SQL filter is incorrectly formatted

NPM 12 bug: Custom SQL filter is incorrectly formatted

Created by Kevin Twomey, last modified by MindTouch on Jun 23, 2016

Views: 2,231 Votes: 3 Revisions: 3

Overview

Custom Resources are are not working when adding in filters after upgrading to NPM v12.0. The following error appears:
Custom SQL filter is incorrectly formatted.

Environment

NPM v12.0

Cause 

  • This is a bug in NPM 12.0.
  • NPM v12 has issues with FILTER in lowercase and sometimes cannot use NODES.
  • Need to use NODESDATA or NODESCUSTOMPROPERTIES instead where applicable.

Resolution

Workaround:

Edit from lowercase and also edit to a a new table structure where applicable.

Nodes.City = London'  (does not work)

NODECUSTOMPROPERTIES.CITY = 'London' (working)
 

Long Term solution:

  • This issue is verified as fixed in NPM 12.1.

  • Filter works correctly for top resources (like Top XX Volumes by Disk Space Used; Top 10 Interfaces by Percent Utilization; Top XX Nodes by Current Response Time etc) via lowercase\capital letters.

 

Last modified

Tags

Classifications

Public