Submit a ticketCall us

AnnouncementsFace your biggest database issues head-on

Our new eCourse helps you navigate SQL Server performance blocks by teaching you how to recognize and deal with the three DBA Disruptors: Performance Hog, Blame Shifter, and Query Blocker. Register today to learn how to defend your environment and fend off menacing disruptions.

Register for your free eCourse.

Home > Success Center > Network Performance Monitor (NPM) > NPM - Knowledgebase Articles > Use node filters

Use node filters

Updated March 6, 2018

Overview

This article describes how to use node filters. When managing or monitoring large numbers of network devices, node list resources can 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.

Environment

NPM 12 and later

Steps

To apply a node filter:

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

Note the following details about using node filters:

  • 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.
  • If you upgraded to Orion Platform version 2015.1.x or later, your custom SQL or SWQL query or filter may no longer work correctly. For a list of database changes from Orion Platform 2014.2 to version 2017.3, including new tables, column changes, or data constraint or data type changes, see the Database Changes spreadsheet.

To filter results to only show nodes that are not Up, use Status<>1

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)

See also:

SQL Filter on Node Category

Use SolarWinds Query Language (SWQL - SWIS)

SQL query examples

Only show Cisco devices: Vendor = 'Cisco'

Only show devices in Atlanta. (Using a custom property named City):

City = 'Atlanta'

Only show devices beginning with "AX3-": Caption Like 'AX3-*'

Only show Nortel devices that are Down:

Vendor Like 'Nortel*' AND Status=2

Only show devices ending in '-TX':

Vendor Like '*-TX'
 

 

Last modified

Tags

Classifications

Public