When defining entities for your custom chart, custom table, or alert, you can use the following methods.
Specific Objects (static selection)
Use this option when you know which objects you want to include in your chart or table.
This is the most straightforward selection method, and recommended for new users. It is also the preferred method for relatively permanent network objects.
Filter or search for the objects you want to include.
Select the objects' check boxes.
Use this option to select objects based on object properties.
This is the preferred selection method for groups of objects of a specified type that may change over time. "All Cisco nodes in Austin" is an example of a group best defined using the Dynamic Query Builder.
Select the type of selector query you want to use (Basic or Advanced).
The Advanced Selector provides access to all network object characteristics, and the Basic Selector provides access to a smaller subset of the most frequently used network object characteristics.
Select the type of objects to report on from the I want to report on drop-down menu.
Specify the condition for displaying objects:
Click Add Condition.
Select All child conditions must be satisfied (AND) or At least one child condition must be satisfied (OR).
Select a property of the monitored object, a conditional relation, and provide a value.
If necessary, add another condition.
For Basic Selector, click Add Simple Condition and repeat previous actions.
For Advanced Selector, click the + sign to add child conditions, and select an option:
- Add Single Value Comparison (Recommended) - The child condition evaluates a single field, like Status
- Add Double Value Comparison - The child condition evaluates two conditions, such as Status and OS
- Add And/Or block - Adds a sub condition block
Use this option if you are comfortable querying your SolarWinds database directly using SQL or SWQL.
SQL queries using the WITH clause are not supported.
Select SQL or SWQL, and enter your query.
The SQL option is disabled for non-administrator accounts, due to security reasons. Moreover, SQL does not respect account limitations and users might see data they shouldn't have access to.
SWQL does not require administrator rights; it respects account limitations.
Click Preview Results to test your query.