When to use Autotune
Use Autotune to improve metric performance when:- A new custom metric isn’t accurate enough for your use case
- An existing metric isn’t generalizing well to a new domain or use case
- An existing metric is producing inconsistent results with low reviewer agreement in production
- The current prompt isn’t handling domain-specific edge cases reliably
- Manual prompt iteration is too time-consuming to scale
How it works
See Autotune in action
1
Review metric results across logs
Examine metric outputs across your logged spans, traces, or sessions where the metric isn’t performing as expected.
2
Identify incorrect outputs
Flag results that are incorrect or do not match your team’s expectations.
3
Enter the expected value and explain why it's correct
For each flagged result, enter the value the metric should have produced and add a natural-language explanation of why.
4
Retune the metric
Run Autotune using the collected feedback. Galileo aggregates the feedback and adapts the metric prompt accordingly.
5
Review and test the updated prompt
Inspect the changes to the prompt and test the updated metric before publishing.
6
Apply the improved metric to future runs
Publish the updated metric so it is used for new logs and evaluations.
You can optionally recompute historical results with the updated metric after publishing.
How to provide good feedback
Autotune supports unlimited feedback per metric. Good feedback should include what output the metric should have produced and why the corrected result is right. Avoid vague corrections:Which metrics are supported?
Autotune works across all LLM-as-a-judge metrics, output types, and metric levels.Related resources
Custom LLM-as-a-Judge Metrics
Learn how to create and configure custom LLM-as-a-judge metrics in the Galileo console.
LLM-as-a-Judge Prompt Engineering Guide
Learn best practices for writing effective metric prompts.
Metrics Overview
Explore Galileo’s comprehensive metrics framework for evaluating and improving AI system performance.