Submit a ticketCall us

Looking to compare latest NPM features with previous versions of NPM?
The NPM new feature summary offers a comparison of new features and improvements offered with this release.

 

 

 

 

Home > Success Center > Network Performance Monitor (NPM) > NPM 12.1 Administrator Guide > Customize resources and charts for NPM > Filter nodes in resources using SQL queries for NPM

Filter nodes in resources using SQL queries for NPM

Table of contents
Created by Caroline Juszczak, last modified by Magdalena.Markova on Dec 12, 2016

Views: 491 Votes: 1 Revisions: 6

When you are managing or monitoring large numbers of network devices, node list resources can easily become very large and difficult to navigate. Filters are optional SQL queries that are used to limit node list displays for easier resource navigation. SQL queries can be made on any predefined or custom properties.

If you have upgraded to Orion Platform version 2015.1.x or later, your custom SQL or SWQL query or filter may no longer work correctly.

  1. Click Edit in any node list resource.
  2. Provide an appropriate SQL query in the Filter Nodes (SQL) field, and click Submit.

SQL Query Examples

By default, node list resources are designed to sort nodes alphabetically by node caption. This configuration cannot be overwritten using a SQL filter, so order by clauses included in SQL filters are redundant and will result in Custom SQL filter formatting errors.

The following are valid status levels:

  • 0 = Unknown (current up/down status of the node is unknown)
  • 1 = Up (The node is responding to PINGs)
  • 2 = Down (The node is not responding)
  • 3 = Warning (The node may be responding, but the connection from the server to the Node is dropping packets)
 
Last modified
03:22, 12 Dec 2016

Tags

Classifications

Public