This page describes how to use the built-in StackState Query Language (STQL) to write advanced topology component filters. STQL queries are used in StackState to write advanced topology filters and can be combined with scripts in the Analytics environment.
Component filters are used in two ways in STQL:
Define the set of components to be included in the query output.
Specify the set of components to be handled by an in-built STQL function.
The filters described below can be combined using boolean operators to achieve complex selections of components. Note that boolean operators will be executed in the standard order: NOT, OR, AND. You can change the order of operations by grouping sections of a query with parentheses (...).
Components in the specified domain(s).
Components in the named environment.
Components with the named health state.
Components with the named labels.
Components in the named layer.
Components with the specified name.
Components of the specified type.
You can use
* as a full wildcard in a component filter. It is not possible to filter for partial matches using a wildcard character.
# Select all componentsname = "*"# Select all components with name "serviceB"name = "serviceB"# Select all components in the "application" layer:layer = "application"# Select all components named either "appA" or "appB" that do not have a label "bck"name IN ("appA","appB") NOT label = "bck"# Select all components named "appA" that do not have a label "bck" or "test"name = "appA" NOT label in ("bck", "test")
The function withNeighborsOf extends STQL query output, adding connected components in the specified direction(s). The number of topology levels included can be adjusted up to a maximum of 15.
withNeighborsOf(components=(), levels=, direction=)
A component filter
The component(s) for which the neighbors will be returned, see component filters.
The number of levels to include in the output. Use "all" to display all available levels (maximum 15)
"up", "down", "both"
up: only components that depend on the named component(s) will be added down: only dependencies of the named component(s) will be added both: components that depend on and dependencies of the named component(s) will be added.
The example below will return all components in the application layer that have a health state of either "CRITICAL" or "DEVIATING". Components with names "appA" or "appB" and their neighbors will also be included.
layer = "application"AND (healthstate = "CRITICAL" OR healthstate = "DEVIATING")OR withNeighborsOf(components = (name in ("appA","appB")))
withCauseOf function has been deprecated. This functionality has been replaced by the Root Cause Analysis section in the visualizer. The construct will be parsed, but will not produce any additional components.