Timestamp when the evaluation rule was created.
Desired enabled state configured by the client.
Evaluator currently used by this rule.
name and scope identify the evaluator family conceptually.
id is the currently active evaluator version in that family.
If you create a newer project version with the same evaluator name later, existing evaluation rules are moved to it automatically.
List of filter conditions used to decide whether a target should be evaluated.
Stable evaluation rule identifier.
Variable mappings used to populate evaluator runtime variables from the live target object.
Human-readable deployment name. This is independent from the evaluator name.
Human-readable explanation when status=paused, otherwise null.
Machine-readable reason when status=paused, otherwise null.
Fraction of matching target objects that should be evaluated.
Must be greater than 0 and less than or equal to 1.
1 means evaluate every matching target.0.25 means evaluate approximately 25% of matching targets.Effective runtime status after Langfuse applies validation and blocking rules.
Target object type that should trigger scoring.
Timestamp when the evaluation rule was last updated.
Live evaluation rule for incoming data.
An evaluation rule answers:
Important status semantics:
enabledis the desired on/off setting from the clientstatusis the effective runtime state after Langfuse applies validation and blocking rulesenabled=truewithstatus=pausedmeans the rule should run, but Langfuse has paused it until the underlying problem is fixedExample