CATALOG_FILTER_EXISTS symbol.
From the backstage docs:
- Each key of a record is a dot-separated path into the entity structure, e.g. metadata.name.
- The values are literal values to match against.
- All matching of keys and values is case insensitive.
- If multiple filter sets are given as an array, then there is effectively an OR between each filter set.
- Within one filter set, there is effectively an AND between the various keys.
- Within one key, if there is more than one value, then there is effectively an OR between them.
filter property) and exclusion (under the exclude property).
YAML
YAML is available for checks, tracks, and collector configs.Examples
Include Filters
Inclusion filters will always be under thefilter property.
Match entities with lifecycle production:
service or website:
component and type of service or website:
Exclude Filters
Exclusion filters will always be under theexclude property, and can used to further refine your results.
An exclusion filter must be used together with an inclusion filter.
Match entities with kind of component where spec.lifecycle is NOT experimental.
component AND (spec.type is NOT dataset OR website) AND (metadata.tags does NOT contain skip).
UI
The UI interface for filters is available to check, track, campaign and collector configs. To make it easier, the UI comes with a few common filter categories. The other category can be used to add any key value filter combination.
Adding a Filter
You add a Kind, Type, Lifecycle, Owner, System, or Tags filter, simply select or search for the options you want and select them.


metadata.name.
Exclude Filter
Exclude filters can be selected by clicking the exclude tab. Exclude filter requires an include filter to function.
Preview
The UI includes a preview of entities that match the given filters. You can toggle this on/off.