> ## Documentation Index
> Fetch the complete documentation index at: https://docs.coval.ai/llms.txt
> Use this file to discover all available pages before exploring further.

# Trace Search

> Search across all traced calls in your organization with natural language queries, structured filters, and Transition Hotspots analysis.

<iframe className="w-full aspect-video rounded-xl" src="https://www.loom.com/embed/c1d437ec33ef4555b38c8b44602b348d" title="Cross-Call Trace Search walkthrough" frameBorder="0" allow="accelerometer; clipboard-write; encrypted-media; gyroscope; picture-in-picture" allowFullScreen />

## Overview

Trace Search lets you query across all traced calls in your organization — both simulations and conversations — from a single page. Instead of inspecting traces one call at a time, you can search by span name, provider, status, duration, attributes, or plain English to find patterns across your entire call history.

Access Trace Search from the **Trace Search** button on the Conversations page, or from the left sidebar under *Observability*.

## Natural Language Search

Type a plain English query into the search bar and Trace Search will interpret it into structured filters automatically. For example:

* `"slowest 10 LLM calls in the last 24 hours"`
* `"errors from NormalAgentName agent in the last two weeks"`
* `"TTS calls longer than 2 seconds"`

The NL search supports sort keywords (`slowest`, `fastest`, `newest`, `oldest`), result limits (`top 10`, `five slowest`), and time expressions.

## Structured Filters

You can also build precise queries using the structured filter controls:

| Filter         | Description                                                                                                   |
| -------------- | ------------------------------------------------------------------------------------------------------------- |
| **Time Range** | Preset options (1h, 3h, 12h, 24h, 3 days, 1 week, 2 weeks, 1 month) or custom date/time pickers               |
| **Span Name**  | Filter by span type (e.g. `llm`, `tts`, `stt`, `llm_tool_call`) with autocomplete from your actual trace data |
| **Provider**   | Filter by service provider with autocomplete suggestions                                                      |
| **Status**     | Filter by span status: `ERROR`, `OK`, or `UNSET`                                                              |
| **Duration**   | Set minimum and/or maximum duration in milliseconds                                                           |
| **Attributes** | Add one or more attribute filters with operators: Contains, Equals, Exists, `>`, `>=`, `<`, `<=`              |
| **Agent**      | Scope results to a specific agent                                                                             |
| **Test Set**   | Scope results to a specific test set                                                                          |

Multiple attribute filters stack with AND logic. Autocomplete suggestions are drawn from your organization's actual trace data in ClickHouse.

## Results

Search results show as cards with:

* Call source (Simulation or Conversation) and timestamp
* Overall span status with color coding
* Total span count and root span duration
* Provider and service metadata
* Direct link to the full trace viewer for each result

An aggregate stats bar at the top shows the total number of matching calls and the error rate across results.

## Transition Hotspots

The **Transition Hotspots** tab shows a failure matrix computed across your filtered search results. This is the same heatmap visualization available on individual runs (see [Transition Hotspots](/concepts/simulations/traces/viewing#transition-hotspots)), but applied across all calls matching your current search filters.

Use this to identify systemic failure patterns that span multiple runs or conversations — for example, a specific state transition that consistently fails across your production traffic.