> ## Documentation Index
> Fetch the complete documentation index at: https://docs.latitude.so/llms.txt
> Use this file to discover all available pages before exploring further.
# Filters
> Use the shared filter system to narrow traces, save searches, and configure evaluation triggers
# Filters
Latitude uses a universal filter system across the platform. The same filters you use to narrow traces in a search also power saved searches and evaluation triggers. Learn it once, use it everywhere.
## How Filters Work
A filter is a set of field conditions. Active conditions combine with **AND** logic. For example, "Status is error" and "Cost is greater than \$1" returns only traces that match both conditions.
Filters appear on the Traces page, in the Search page (alongside the search query), and in the configuration UI for evaluation triggers.
## Available Filter Fields
| Field | Description | Example |
| ----------------- | -------------------------------------------------- | ---------------------------------- |
| **Status** | Trace completion status: OK, ERROR, or UNSET | `status in [error]` |
| **Name** | Root span name (the `path` you set in `capture()`) | `name eq "invoke_agent"` |
| **Session ID** | Filter to a specific multi-turn session | `sessionId eq "session-abc"` |
| **User ID** | End-user identifier from telemetry metadata | `userId eq "user-42"` |
| **Tags** | Custom tags attached to spans | `tags in ["production", "canary"]` |
| **Models** | LLM models used in the trace | `models in ["gpt-4o"]` |
| **Providers** | LLM providers called | `providers in ["openai"]` |
| **Services** | OpenTelemetry service names | `serviceNames in ["api-server"]` |
| **Cost** | Estimated total trace cost | Cost greater than `$1` |
| **Duration** | End-to-end trace duration | Duration greater than `5s` |
| **TTFT** | Time to first token | TTFT greater than `1s` |
| **Span Count** | Number of spans in the trace | `spanCount gte 10` |
| **Error Count** | Number of errored spans | `errorCount gte 1` |
| **Tokens Input** | Total input tokens across LLM calls | `tokensInput gte 1000` |
| **Tokens Output** | Total output tokens across LLM calls | `tokensOutput gte 500` |
| **Metadata** | Custom key-value metadata your application sends | `metadata.env eq "production"` |
## Operators
Filters support 10 operators:
| Operator | Meaning | Works With |
| ------------- | ---------------------------------- | ----------------------------------------- |
| `eq` | Equals | All fields |
| `neq` | Not equals | All fields |
| `gt` | Greater than | Numeric fields |
| `gte` | Greater than or equal | Numeric fields |
| `lt` | Less than | Numeric fields |
| `lte` | Less than or equal | Numeric fields |
| `in` | Value is in set | Status, tags, models, providers, services |
| `notIn` | Value is not in set | Status, tags, models, providers, services |
| `contains` | Substring match (case-insensitive) | Text fields, metadata |
| `notContains` | Substring does not match | Text fields, metadata |
## Custom Metadata Filters
Your application can send structured metadata with its telemetry. Filter on any metadata field using dot-notation:
* `metadata.env`: top-level key
* `metadata.runtime.region`: nested key
Metadata filters support exact matches, ranges, set membership, and substring searches on your custom fields.
## Combining Filters
All active filters combine with **AND** logic. Common combinations:
* **Status** = ERROR **and** **Cost** > \$1: find expensive failures
* **Models** = gpt-4o **and** **Duration** > 5s: find slow GPT-4o traces
* **Metadata** `environment` = `production` **and** **Error Count** > 0: find production errors
* **Tags** in `["canary"]` **and** **Tokens Output** > 2000: find verbose canary responses
## Where Filters Are Used
| Feature | How Filters Are Used |
| ---------------------------------------------- | ------------------------------------------------------------------ |
| **Trace dashboard** | Interactive filtering from the toolbar |
| **[Search](../search/overview)** | Narrow a search query to a specific subset of traces |
| **[Saved searches](../search/saved-searches)** | The filter set is part of what gets bookmarked alongside the query |
| **Evaluation triggers** | Define which traces an evaluation monitors |
| **Score analytics** | Narrow analytics dashboards to specific trace subsets |
When you configure an evaluation trigger or save a search, you're building a filter using this same system. An empty filter means "match all traces."
## Next Steps
* [Traces](./traces): Browse and filter your traces
* [Search](../search/overview): Combine filters with hybrid search
* [Saved Searches](../search/saved-searches): Persist a query plus filter set as a named bookmark
* [Evaluation Triggers](../evaluations/triggers): Use filters to control evaluation scope