DocsEvaluationConcepts

Core Concepts

This page digs into the different concepts of evaluations, and what’s available in Langfuse.

Ready to start?

The Evaluation Loop

LLM applications often have a constant loop of testing and monitoring.

Experiments let you test your application against a fixed dataset before you deploy. You run your new prompt or model against test cases, review the scores, iterate until the results look good, then deploy your changes.

Online evaluation scores live traces to catch issues in real traffic. When you find edge cases your dataset didn’t cover, you add them back to your dataset so future experiments will catch them.

Online and offline evaluation loop

Here’s an example workflow for building a customer support chatbot

  1. You update your prompt to make responses less formal.
  2. Before deploying, you run an experiment: test the new prompt against your dataset of customer questions.
  3. You review the scores and outputs. The tone improved, but responses are longer and some miss important links.
  4. You refine the prompt and run the experiment again.
  5. The results look good now. You deploy the new prompt to production.
  6. You monitor with online evaluation to catch any new edge cases.
  7. You notice that a customer asked a question in French, but the bot responded in English.
  8. You add this French query to your dataset so future experiments will catch this issue.
  9. You update your prompt to support French responses and run another experiment.

Over time, your dataset grows from a couple of examples to a diverse, representative set of real-world test cases.

Experiments

An experiment runs your application against a dataset and evaluates the outputs. This is how you test changes before deploying to production.

Definitions

Before diving into experiments, it’s helpful to understand the building blocks in Langfuse: datasets, dataset items, scores, tasks, evaluators, and experiments.

ObjectDefinition
DatasetA collection of test cases (dataset items). You can run experiments on a dataset.
Dataset itemOne item in a dataset.Each dataset item contains an input (the scenario to test) and optionally an expected output.
TaskThe application code that you want to test in an experiment. This will be performed on each dataset item, and you will score the output.
EvaluatorA function that scores experiment results. In the context of a Langfuse experiment, this can be a deterministic check, or LLM-as-a-Judge.
ScoreThe result of an evaluator. This can be numeric, categorical, or boolean. See Scores for more details.
Experiment RunA single execution of your task against all items in a dataset, producing outputs (and scores).

You can find the data model for these objects here.

How these work together

This is what happens conceptually:

When you run an experiment on a given dataset, each of the dataset items will be passed to the task function you defined. The task function is generally an LLM call that happens in your application, that you want to test. The task function produces an output for each dataset item. This process is called an experiment run. The resulting collection of outputs linked to the dataset items are the experiment results.

Often, you want to score these experiment results using different evaluators. These evaluators take in the dataset item and the output produced by the task function, and produce a score based on a specific criteria you define. Based on these scores, you can then get a complete picture of how your application performs across all test cases.

Experiments flow

You can compare experiment runs to see if a new prompt version improves scores, or identify specific inputs where your application struggles. Based on these experiment results, you can decide whether the change is ready to be deployed to production.

You can find more details on how these objects link together under the hood on the data model page.

Two ways to run experiments

You can run experiments programmatically using the Langfuse SDK. This gives you full control over what the task, evaluator, etc. look like. Learn more about running experiments via SDK.

Another way is to run experiments directly from the Langfuse interface by selecting a dataset and prompt version. This is useful for quick iterations on prompts without writing code. Learn more about running experiments via UI.

Online Evaluation

For online evaluation, evaluators are triggered to produce a score on production traces. This helps you catch issues immediately.

Langfuse currently supports LLM-as-a-Judge and human annotation checks for online evaluation. Deterministic checks are on the roadmap.

Monitoring with dashboards

Langfuse offers dashboards to monitor your application performance in real-time. You can also monitor scores in dashboards. You can find more details on how to use dashboards here.

Evaluation Methods

For both experiments and online evaluation, you can use a variety of evaluation methods to add scores to traces, observations, sessions, or dataset runs.

MethodWhatUse when
LLM-as-a-JudgeUse an LLM to evaluate outputs based on custom criteriaSubjective assessments at scale (tone, accuracy, helpfulness)
Scores via UIManually add scores to traces directly in the Langfuse UIQuick quality spot checks, reviewing individual traces
Annotation QueuesStructured human review workflows with customizable queuesBuilding ground truth, systematic labeling, team collaboration
Scores via API/SDKProgrammatically add scores using the Langfuse API or SDKCustom evaluation pipelines, deterministic checks, automated workflows
Was this page helpful?