Unable to view Scores under Evaluation tab #15612
Replies: 3 comments 2 replies
|
Any suggestions |
|
Based on your description, your scores are attached to traces correctly (visible in Tracing), but not appearing in Evaluation → Scores or Scores → Analytics. Here are the key things to check: 1. Verify Score Data TypeScore Analytics only supports numeric, categorical, and boolean scores. Text scores are not supported in Score Analytics because free-form text cannot be meaningfully aggregated or compared.(1) When you push scores via the SDK, ensure you're specifying the correct langfuse.create_score(
name="answer_relevancy",
value=0.9,
trace_id="your_trace_id",
data_type="NUMERIC",
)2. Check Object Type Selection in AnalyticsIn Score Analytics, you need to select the correct object type (Traces, Observations, Sessions, or Dataset Run Items) that matches where your scores are attached.(1) If you attached scores directly to traces, select "Traces" as the object type. If you're looking at dataset runs specifically, select "Dataset Run Items."(1) 3. Verify Time RangeEnsure your selected time range in Score Analytics includes the period when the scores were created. Use the date picker to set an appropriate range (e.g., "Past 90 days").(1) 4. Score Name MatchingWhen selecting a score in the Analytics dropdown, the score name must exactly match what you used when creating the score via the SDK.(1) 5. Dataset Run ScoresIf you want scores to appear on dataset runs specifically, you need to link the score to the dataset run item, not just the trace. When scoring production traces, For dataset experiments, scores attach to each item's trace and to the dataset run when using the experiment SDK.(3) Recommended Troubleshooting Steps
If scores still don't appear, verify in the Langfuse UI under Evaluation → Scores (the table view) that the scores are listed there first before checking Analytics. 📚 Sources: Have another question? Just tag @inkeep. |
|
Hi, I ran into a very similar (maybe the same) issue. I fixed it by changing how evaluation is run. In my case, the problem was that scores were being attached to each individual trace instead of to the experiment/dataset run itself. Once I stopped doing that and attached the score to the experiment, the issue went away. Worth checking your Langfuse setup, you might need to update it too. The key change: when you run the experiment, pass an from langfuse import get_client
langfuse = get_client()
def my_evaluator(*, input, output, expected_output, **kwargs):
return {
"name": "accuracy",
"value": 1 if output == expected_output else 0,
}
result = langfuse.run_experiment(
name="my-experiment",
data=my_dataset,
task=my_task,
evaluators=[my_evaluator], # <-- this is the fix, avoid create_score
)
print(result.format())This is documented in Langfuse's guide on run-level evaluators that assess the full experiment results and compute aggregate metrics, which when run on Langfuse datasets get attached to the full dataset run for tracking overall experiment performance here: https://langfuse.com/faq/all/retrieve-experiment-scores Hope that helps! |



Hi, I ran into a very similar (maybe the same) issue. I fixed it by changing how evaluation is run.
In my case, the problem was that scores were being attached to each individual trace instead of to the experiment/dataset run itself. Once I stopped doing that and attached the score to the experiment, the issue went away. Worth checking your Langfuse setup, you might need to update it too.
The key change: when you run the experiment, pass an
evaluatorsargument (notcreate_score). Each evaluator should be a function that returns an evaluation object containing your metric (e.g.name,value,comment), and Langfuse will handle attaching it correctly to the experiment run: