Skip to main content
Applies to:
  • Plan -
  • Deployment -

​
Summary

Goal: Configure online scoring rules to run on trace-level data instead of individual spans. Features: Online scoring rules, Scope toggle, span filtering, root span data. If your automation rule editor shows a Scope toggle with Trace/Span options, set it to Trace. This is the simplest way to run scorers on trace-level data. The Scope toggle requires data plane v2.0.0+ for self-hosted deployments. If you don’t see it, use Option 2 below.

​
Option 2: Add “All root spans” filter

If the Scope toggle isn’t available on your deployment, you can restrict scoring to root spans using the “All root spans” filter:
  1. Open your project and go to Settings > Automations.
  2. In the scoring rule, click Add filter and select All root spans.
  3. Click Test rule to verify the scorer receives the expected data from the root span.
All root spans filter configuration This is a span-level filter, not true trace scope. It restricts the scorer to root spans only, which typically contain the consolidated data (input, output, metadata) you need. For full trace-scoped execution, use Option 1 when available.

​
Why This Is Needed

By default, scorers run on individual spans. When your data is consolidated at the trace level (root span), the scorer needs to target root spans to access it.