The filter field is a powerful tool that allows you to quickly find relevant information or narrow down results within apps.
AND
connected.X
on the rightmost end of the field.X
for that statement.To make things easier, the interface offers suggestions.
.
as a decimal separator.key = value
.Note: Some features may not be available in all filter fields due to performance or data source limitations. For example, while you can use wildcards (an asterisk *
) at the beginning (ends-with), at the end (starts-with), or both (contains) of a value, certain implementations, like those based on the classic entity selector API, might not support the ends-with option.
Filter syntax
Description
Example
=
equals
key = value
!=
not equals
key != value
<
less than
key < value
<=
less than or equal to
key <= value
>
greater than
key > value
>=
greater than or equal to
key >= value
= *
has any value
key = *
!= *
doesn’t have a value
key != *
in
matches one or more values in a list of values
key in (value1, value2)
not in
doesn’t match one or more values in a list of values
key not in (value1, value2)
Filter syntax
Description
Example
AND
optional Both of the expressions must be true.
Note: AND
is optional because it's implicit between two expressions.
key = value key2 = value
Alternative:
key = value AND key2 = value
OR
One of the expressions must be true.
key = value OR key2 = value
Use parentheses ( )
to group filter statements logically, such as key = value OR (key2 = value key3 = value)
.
Spaces, =
, <
, and >
are special characters in the filter field. Double quotes "
and *
are also special characters when used at the start or end of a key or value. To use special characters as part of a value, you need to escape them.
Escape options:
Wrap the corresponding key or value in quotation marks. In the following example, the spaces between Product
and Name
, and between Widget
and A
, are escaped by wrapping the values in quotation marks.
"Product Name" = "Widget A"
Escape a single character with a backslash \
. In the following example, the asterisk on the right end is escaped with a backslash. This means it isn't interpreted as a wildcard.
key = openshift-service-serving-signer@1677006647\*
.
String values are case-sensitive for all operators.
A wildcard matches any number of characters in a value and is indicated by an asterisk *
.
Wildcard syntax
Description
key = *value
ends with value
key = value*
starts with value
key = *value*
contains value
When a value contains special characters like spaces, you need to escape the value to ensure it is correctly interpreted. In such cases, wildcards need to be used outside the escaped value. Here's an example:
Suppose you want to filter for a service named "Payment Service". You would write the filter like this:
Name = "Payment Service"
This ensures that the entire string "Payment Service" is treated as a single value, including the space.
Similarly, if you want to use wildcards with a value that contains spaces, you can do it like this:
Name = *"Payment Service"*
This filter will match any service name that contains "Payment Service" anywhere within the name.
In some cases, crafting complex filter statements is not required. For this purpose, a slimmed-down, more focused version of the filter syntax is available. Filter fields with basic syntax don't support a logical OR
and grouping filter statements with brackets ()
.
While the filter field provides a user-friendly interface, the Dynatrace Query Language (DQL) offers more advanced capabilities. For complex use cases, we recommend writing a custom DQL query. DQL allows you to harness additional features and fine-tune your queries beyond what the filter field provides.
Filter syntax
DQL
=
matchesValue(key, "value", caseSensitive: true)
!=
not matchesValue(key, "value", caseSensitive: true)
<
<
<=
<=
>
>
>=
>=
= *
isNotNull()
!= *
isNull()
in
key in (value1, value2)
in
not in
key not in (value1, value2)
not in
*value
matchesValue(key, "*value", caseSensitive: true)
value*
matchesValue(key, "value*", caseSensitive: true)
*value*
matchesValue(key, "*value*", caseSensitive: true)
The logical operators AND
and OR
are case insensitive. You can use and
and or
for the filter syntax and the DQL syntax.