Trace-scoped automation scores missing from Monitor charts

Applies to:

Plan - Any
Deployment - Any
Use case - Show trace-scoped automation scores from online processing or rewinds by score-write date, or report rewound scores by original trace date.

Summary

Trace-scoped scoring automations write score-bearing rows without a metrics.start value during normal online processing and rewinds. Preset Scores charts exclude those rows when Use metrics.start for monitor charts time bucketing is enabled. Turn off that setting to show these scores by their created date. For scores written during a rewind, use the two-stage SQL query below if you need a manual report grouped by the original trace date.

What is happening

The preset Scores chart reads the score-bearing rows directly. When Use metrics.start for monitor charts time bucketing is enabled, the chart applies exact metrics.start bounds. Because rows written by trace-scoped scoring automations do not have metrics.start, the chart excludes them even though the scores remain visible on their traces. This applies during normal online processing and rewinds. When the setting is disabled, Monitor charts use created instead. This shows scores on the date the automation wrote them. Rewound scores appear on the rewind date, not the dates the source traces ran.

Fix or suggestion

Option 1: Show scores by score-write date

Before you change this setting: This project-level setting also changes the time dimension for other Monitor time-series charts. The preset Topics summary chart continues to use created.

Go to Settings > Project.
Under Monitor charts time bucketing, turn off Use metrics.start rather than created for monitor chart time dimensions. The setting saves when you turn it off.
Refresh the dashboard and select a time range that includes when the automation wrote the scores.

The preset Scores chart now shows the trace-scoped automation scores by their created timestamp.

Option 2: Create a manual report by original trace date

Use the Query page when you need to inspect scores written during a rewind by the dates the source traces ran. Replace the project ID, scorer name, and date range. Use the smallest practical created range that covers both the original trace ingestion and the later rewind because wide ranges can be expensive to query.

SELECT
  date_trunc('day', to_datetime(trace_start)) AS trace_day,
  avg(score_value) AS avg_score,
  count(*) AS trace_count
FROM (
  SELECT
    root_span_id,
    min(metrics.start) AS trace_start,
    avg(scores."<SCORER_NAME>") AS score_value
  FROM project_logs('<PROJECT_ID>')
  WHERE created >= '<START_DATE>'
    AND created < '<END_DATE>'
  GROUP BY root_span_id
) AS per_trace
WHERE trace_start IS NOT NULL
  AND score_value IS NOT NULL
GROUP BY date_trunc('day', to_datetime(trace_start))
ORDER BY trace_day;

The inner query combines the trace’s earliest metrics.start with its score. The outer query groups those per-trace values by the original trace date. If a trace contains multiple values for the named scorer, avg(scores."<SCORER_NAME>") averages them. This is a manual SQL report. It does not create a persistent Monitor chart or alert.

How to confirm it worked

After Option 1, confirm the preset Scores chart shows data on the date the automation wrote the scores.
After Option 2, confirm trace_day matches the original trace dates and the returned scores match the historical traces you expect.

Notes

With metrics.start bucketing enabled, preset Scores charts exclude trace-scoped automation scores because those rows do not contain metrics.start.
This article does not apply to span-scoped scoring automations, which write scores to matching spans that have metrics.start.
Use the SQL approach only when a manual trace-date report meets your needs.

​Summary

​What is happening

​Fix or suggestion

​Option 1: Show scores by score-write date

​Option 2: Create a manual report by original trace date

​How to confirm it worked

​Notes

Summary

What is happening

Fix or suggestion

Option 1: Show scores by score-write date

Option 2: Create a manual report by original trace date

How to confirm it worked

Notes