Skip to main content
When you create a metric with the Full Trace (selected spans) input type, Galileo evaluates only the child spans you select rather than the entire trace. This reduces cost and noise when only a subset of spans carries the signal you care about.

​
How it works

A trace can contain many spans — LLM calls, tool calls, retriever lookups, and custom spans. By default, most input types send the full trace context to the evaluator. With selected spans, you define one or more span names. Galileo then:
  1. Traverses all child spans in the trace recursively.
  2. Collects spans whose names exactly match any of the names you provided (OR logic).
  3. Sends only the matching spans as the evaluator input.
If a matching span itself has children, those children are included as a pruned subtree — only the matching descendants are kept. If no spans in a trace match, the metric returns not_applicable for that trace and no cost is incurred.

​
When to use selected spans

Use the standard Full Trace (I/O) input type when you need the complete conversation context to make an accurate judgment.

​
Create a metric with selected spans

1

Navigate to the Metrics page

From the Galileo main menu, select Metrics, then select Create metric.
2

Select the input type

Under Apply to, select Full Trace (selected spans).A Span filters section appears below the input type selector.
3

Add span names

Enter the exact name of each span you want to include. For example, enter web_search to include only spans named web_search.Select Add filter to add more span names. A span is included if it matches any of the names you enter.
4

Configure the rest of the metric

Complete the metric configuration as usual — write your evaluation question or prompt, set the output type, and configure the model.
5

Test and save

Select Test metric to verify the metric runs correctly against sample traces, then select Create Metric.

​
Cost impact

The metric only processes matched spans, so token usage scales with the size of those spans rather than the full trace. For a trace with many spans where only a few are relevant, this can reduce cost significantly.
If no spans in a trace match your filters, the metric returns not_applicable for that trace. This does not count as a failed evaluation and does not incur cost.