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

​
Summary

Issue: An unexpected score column appears in Logs after an online scorer automation runs, or remains visible after an automation or scorer was deleted. Cause: Logs can show score columns from two related sources. First, Braintrust may include a column for configured project score names, including online scoring rule names. Second, when an online scorer runs, its result is written to the log row under scores.<name>. That persisted score key comes from the scorer function name or the scorer’s returned score name, not from the rule name unless those names happen to match. Resolution: Check both the online scoring rule name and the scorer function output. Renaming the rule changes the rule-name column that gets added to the Logs table from the rule’s configuration. Renaming the scorer function, or returning explicit { name, score } objects, changes the score keys written to future log rows. Existing log rows are not rewritten, so historical score columns may remain visible while those rows exist.

​
How score columns are named

When an online scorer runs, Braintrust writes the scorer result into the log row’s scores object. If the scorer returns a single value (a number, true/false, or null): 
return 1;
Braintrust uses the scorer function’s name as the score key. It does not use the online scoring rule name unless the scorer function happens to have the same name. If the scorer returns a score with an explicit name: 
return { name: "correctness", score: 1 };
Braintrust uses that name field as the score key. If the scorer returns multiple named scores: 
return [
  { name: "coverage", score: 0.8 },
  { name: "conciseness", score: 1 },
];
Braintrust writes one score key for each returned name. The scorer function’s name is not used here — only the returned name values become column keys.

​
What to check

Use these checks to track down the source of the unexpected column.
  • Confirm whether the column appears on new logs, only on historical logs, or both
  • Review active rules in Settings > Automations
  • Compare the unexpected column name against the rule name, the scorer function name, and any names returned by the scorer
  • If the unwanted column is empty and matches a rule’s name, rename the rule
  • If the unwanted column contains actual score values, rename the scorer function or change the names it returns
  • Refresh Logs and verify the behavior against a newly created log row

​
Notes

  • Deleting an automation stops future runs and removes the corresponding column from the Logs table. It does not remove score values already written to past log rows. The same is true if you rename or delete a scorer — historical rows are not rewritten.
  • A column can stay visible as long as the rows currently in view still contain that score in their data
  • If you’ve changed a rule or scorer and the Logs table looks out of date, a hard refresh in your browser forces the UI to reload the latest configuration