Filtering
Filters narrow down the rows that go into each aggregation and group. They are AND-combined; there is no OR-group support. The server enforces a per-field operator allow-list, so the exact subset of operators you can use depends on the field.Filter object structure
- Field filters
- Metadata filters
For standard datasource fields, use
fieldName:Filterable fields
Cache metrics share the underlying table with model metrics, so all model filter fields are also reachable here. The cache-specific fields are
cacheType, cacheNamespace, cacheLookupStatus, and the cache token columns. cacheType is narrow (IN/NOT_IN only); the others accept the full string or numeric operator set as documented below.
For non-cache-specific model fields (e.g.
costInUSD aggregations or errorCode filters), see also the Model Metrics filtering page.
Filter operators
String field operators
Numeric field operators
Boolean field operators
Array field operators (used by team)
Custom metadata filtering and grouping
Every datasource supports filtering and grouping by custom request-metadata keys:- Filter:
{ "metadataKey": "environment", "operator": "EQUAL", "value": "prod" } - Group: include
"metadata.environment"in thegroupByarray.
Implicit team unnesting
Whenteam is in groupBy (or used as the column of an aggregation), the server transparently UNNESTs the Teams array CTE before applying RBAC. Callers don’t need to do anything extra. Rows whose Teams array is NULL or empty drop out naturally.