All Products
Search
Document Center

AgentLoop:Evaluation result fields

Last Updated:Aug 31, 2026

After an AgentLoop evaluation task completes, the result of each evaluator is written as a single log entry to the evaluation_detail Logstore. The Logstore belongs to the Alibaba Cloud Simple Log Service (SLS) project that corresponds to your AgentSpace. This topic describes the type and meaning of each field in the Logstore.

Key concepts

  • Evaluation task: An evaluation configuration that you create. It contains definitions such as the data source, evaluators, and scheduling policy.

  • Run: An actual execution of an evaluation task. A run can be manually triggered or automatically scheduled within a continuous evaluation window.

  • Evaluator: A unit that scores or judges data. A task can contain multiple evaluators, and each evaluator produces one result log entry.

  • Evaluation result: The score, judgment, and explanation that a single evaluator produces for a single piece of data. Each evaluation result is one log entry in the evaluation_detail Logstore.

Common fields

The following fields are common to every evaluation result log entry. Some fields have a value only in specific modes.

FieldTypeDescription
timestamplongThe time when the evaluation result was generated. Unit: milliseconds.
task_idtextThe ID of the evaluation task.
eval_idtextThe unique ID of an evaluation result.
eval_base_idtextThe ID of the evaluation data. It links the evaluation queue to the result record.
run_idtextThe ID of the run.
window_idtextThe ID of the continuous evaluation window. This field has a value only in continuous evaluation mode.
user_idlongThe user ID.
region_idtextThe region.
agentSpacetextThe AgentSpace identifier.
statustextThe evaluation status. Valid values: success, failed, and unknown.

Task and run information

The following fields describe the task and run context of the evaluation result.

FieldTypeDescription
task_nametextThe name of the evaluation task.
task_modetextThe task mode. Valid values: batch, oneshot (one-time), and stream (streaming).
run_nametextThe name of the run.
run_typetextThe run type. Valid values: backfill and continuous.
channeltextThe source of the task. Valid values: default, experiment, and AgentRun (triggered by AgentRun).
data_start_timelongThe start time of the data range for the current run. Unit: milliseconds.
data_end_timelongThe end time of the data range for the current run. Unit: milliseconds.
eval_latencylongThe end-to-end duration from run creation to result generation. Unit: milliseconds.

Evaluation result

The following fields describe the score, judgment, and explanation that a single evaluator produces.

FieldTypeDescription
evaluator_nametextThe name of the evaluator.
evaluator_display_nametextThe display name of the evaluator.
score_nametextThe score name, which identifies the metric item that the evaluator produces.
score_valuedoubleThe raw score value of the evaluator.
normalized_score_valuedoubleThe normalized score, in the range of 0 to 1. This field has a value only when a score range is configured for the evaluator.
score_rangetextThe raw score range, in the [min,max] format.
result_typetextThe result type. Valid values: score (numeric scoring), binary (binary judgment), and text.
explanationtextA human-readable explanation of the score.
evaluation_processtextThe derivation process of the score and explanation.
trajectory_summarytextThe turn-by-turn trajectory summary of the session. This field has a value only for relevant evaluation results.

Error information

When the evaluation status is failed, the following fields record the cause of the failure.

FieldTypeDescription
error_codetextThe error code of the failure.
error_messagetextThe error message that describes the failure cause.

Data association (data_link)

data_link is a JSON field that records the association information of the evaluated data. You can use this field to trace the raw data source of an evaluation result.

FieldTypeDescription
dataset_idtextThe ID of the dataset.
dataset_item_idtextThe ID of the item in the dataset.
trace_idtextThe trace ID of the evaluated data.
span_idtextThe span ID of the evaluated data.
session_idtextThe session ID of the evaluated data.
experiment_idtextThe ID of the experiment.
service_idtextThe ID of the evaluated application.
service_nametextThe name of the evaluated application.
agent_nametextThe name of the evaluated agent.
data_scopetextThe data granularity. Valid values: span, trace, session, log, and dataset.
start_timetextThe start of the time range of the evaluated data.
end_timetextThe end of the time range of the evaluated data.
plan_idtextThe ID of the experiment plan.
projecttextThe SLS project from which the log data comes.
logstoretextThe SLS Logstore from which the log data comes.
logstore_item_idtextThe ID of the log entry.
experiment_group_nametextThe name of the experiment group.
plan_nametextThe name of the experiment plan.
record_idtextThe ID of the record.
record_nametextThe name of the record.
run_envtextThe runtime environment.

Evaluator metadata (eval_meta)

eval_meta is a JSON field that records the invocation metadata generated during evaluator execution.

FieldTypeDescription
model_nametextThe name of the model used for evaluation.
evaluator_request_idtextThe request ID of the evaluator invocation.
evaluator_trace_idtextThe trace ID of the evaluator's own execution. This field is not the trace_id of the evaluated data.
evaluator_log_idtextThe log ID of the evaluator invocation.
evaluator_thread_idtextThe thread ID of the evaluator session.

Evaluator metrics (eval_metrics)

eval_metrics is a JSON field that records the token consumption and duration of the evaluator execution.

FieldTypeDescription
input_tokenslongThe number of input tokens.
output_tokenslongThe number of output tokens.
total_tokenslongThe total number of tokens.
latencylongThe execution duration of a single evaluator. Unit: milliseconds.

Evaluator input (eval_info)

eval_info is a JSON field that records the actual variable values that are passed to the evaluator. Each key corresponds to a variable name defined in the evaluator's variableMapping, and each value is the actual value of that variable.

For example, if the evaluator is configured with the following variable mapping:

{
  "variableMapping": {
    "input": "question",
    "expected": "label"
  }
}

eval_info contains the following content:

{
  "input": "The actual value of the question field",
  "expected": "The actual value of the label field"
}

Custom outputs (custom_outputs)

custom_outputs is a JSON field that stores custom outputs in addition to the standard results of the evaluator. The structure of this field is defined by the evaluator and has no fixed schema.