Issue fields & filters
Filter options, table columns, field values, and limits for the Error Feed's issue list
Feed filters
UI controls on the feed’s filter bar that pick from a fixed set of values, with the exact options each one offers. The filter bar also carries a project select, scoped to your org’s projects, and a free-text Search errors box; this table covers only the selects with a fixed set of options.
| Filter | Options |
|---|---|
| Time range | Last 24 hours, Last 7 days, Last 14 days, Last 30 days, Last 90 days |
| Status | All Statuses, see Status values below |
| Severity | All Severities, see Severity values & priority below |
| Fix layer | All Fix Layers, Prompt, Tools, Orchestration, Guardrails |
Sort keys & directions
The sort_by values the feed list enforces, and the feed table column header that triggers each one. The feed table only sorts on Severity, Events, and Last seen, so first_seen and error_count aren’t reachable from the UI at all.
sort_by | Column header | Default |
|---|---|---|
last_seen | Last seen | Default |
first_seen | Not exposed in the UI | |
error_count | Not exposed in the UI | |
unique_traces | Events | |
severity | Severity |
sort_dir takes asc or desc, and defaults to desc.
Status values
The full set of values an issue’s status can hold, used by both the UI filter and the feed’s status value. See Severity & Status for what each one means.
| Status | Label |
|---|---|
escalating | Escalating |
for_review | For review |
acknowledged | Acknowledged |
resolved | Resolved |
Severity values & priority
The full set of values an issue’s severity can hold, used by both the UI filter and the feed’s severity value, and the priority value each is stored as.
| Severity | Label | Stored as |
|---|---|---|
critical | Critical | urgent |
high | High | high |
medium | Medium | medium |
low | Low | low |
Fix layers
The fix layers a finding can point at; used by both the UI filter and the feed table’s Fix Layer column. See Error taxonomy for the full group-to-category breakdown behind each one.
| Fix layer |
|---|
| Prompt |
| Tools |
| Orchestration |
| Guardrails |
Source values
Where an issue’s underlying finding came from, and what each source value means.
| Source | Meaning |
|---|---|
scanner | Default source |
eval | Set when an eval failure produced the finding; eval-sourced findings also carry an eval_target_type of span, trace, or session |
Event count & time fields
Fields on an issue that count its events and place it in time.
| Field | Counts |
|---|---|
total_events | Every occurrence of the issue |
unique_traces | Distinct traces the occurrences fall across |
unique_users | Distinct users who hit the issue |
first_seen | Time of the issue’s earliest occurrence |
last_seen | Time of the issue’s most recent occurrence |
Traces tab columns & aggregates
UI columns and summary cards on an issue’s Traces tab.
| Column |
|---|
| Trace ID |
| Input |
| Start Time |
| Duration |
| Tokens |
| Cost |
| Score |
| Aggregate card |
|---|
| Total traces |
| Avg score |
| Avg turns |
| P50 latency |
| P95 latency |
List & query limits
Values and bounds the feed and its tabs enforce: page sizes, default and maximum result counts, and the trends day window. A dash means that bound doesn’t apply, only the minimum shown is enforced. The limit parameter appears twice below because it’s bound differently on different surfaces of the app; the Applies to column says which surface each row’s bounds belong to.
| Parameter | Applies to | Min | Default | Max |
|---|---|---|---|---|
limit | Feed list | 1 | 25 | 200 |
offset | Feed list | 0 | 0 | – |
time_range_days | Feed list | 1 | – | – |
limit | Traces tab | 1 | 50 | 500 |
rep_limit | Overview | 1 | 20 | 200 |
days | Trends | 1 | 14 | 90 |
| Feed table page size (UI) |
|---|
| 10 |
| 25 |
| 50 |
Keep exploring
Questions & Discussion