Skip to main content
Let your agent set this up. Copy the evaluations prompt into your coding agent to get started automatically.
A monitor is an evaluator attached to your production traffic. It scores the traces your live application sends, so you see quality and safety problems on real traffic and collect the failing cases to fix. To score a dataset before you deploy a change, see Experiments.

How it works

  1. Your application sends traces to LangWatch through an SDK or OpenTelemetry.
  2. Each monitor checks its preconditions and its sampling rate against the incoming trace.
  3. The monitor runs its evaluator on the trace, or on the whole thread once the thread goes idle.
  4. The result lands on the trace and in the evaluations analytics, where an automation can pick it up.
The evaluator runs after the response is sent. A monitor never delays or blocks a response. To block a request, run the evaluator as a guardrail from your code.

When to use online evaluation

Monitors and guardrails

Create a monitor

  1. Open Online Evaluations and click New Online Evaluation.
  2. Pick an evaluator category and an evaluator, name it and map its inputs to the trace.
  3. Pick Trace Level or Thread Level, add preconditions and a sampling rate if you need them, and click Create Online Evaluation.
The full walkthrough, with the thread-level options and where the results show, is in Setting up Monitors.

Add scores from your code

Your own code can record an evaluation result on the current span, next to the results of the monitors:
See Custom scoring for the result fields.

Next steps

Setting up Monitors

Evaluators

Automations

Guardrails

Last modified on September 8, 2026