Public Preview

DigitalOcean Learning Services

Find out where your agents and models fail in production, then test the fix before it ships. Signals watches traffic on Managed Agents and Serverless Inference and flags the sessions that went wrong, with nothing extra to instrument. Evaluations and Simulations test your change on realistic multi-turn scenarios built from those sessions or from your agent's configuration.

Why improving agents is harder than building them

Monitoring says "up." Users say "wrong."

Standard observability tells you the system was up and latency was fine. It can’t tell you the model gave a confidently wrong answer, the agent picked the wrong tool, or a frustrated user gave up. The tool call returned 200 — it just returned the wrong region. The conversation completed — the user left annoyed.

Finding the problem means reading transcripts

Raw trace volume can exceed 100 GB/s. Grading every session with an LLM judge is prohibitively expensive, and manual review doesn’t scale at all. Most teams learn about failures when a support ticket arrives.

Testing the fix means inventing reality

Hand-built tests cover a narrow slice of real behavior. Synthetic test sets aren’t grounded in your agent or your users. Live traffic is realistic, but users pay for the mistakes. And single-response evals miss the failures that only show up across turns: a prompt tweak fixes step two and quietly breaks step five, or a fine-tuned model scores well on in training and regresses in real conversations.

Stop reading transcripts to find out what broke

Signals finds the agent and model sessions that went wrong in production and turns them into evaluations you can run. Nothing extra to instrument.

Agent and inference observability

Signals (Public Preview)

Signals efficiently finds the agent and inference sessions that went wrong in production and turns them into evaluations you can run. Nothing extra to instrument.

For agents on Managed Agents and models served through Serverless Inference.

  • Stitches conversation turns into sessions using events that Serverless Inference, Harness Runtime, and Action Gateway already emit.
  • Classifies sessions across three dimensions: Interaction (user sentiment, corrections, escalations, quits), Execution (invalid tool arguments, retry loops), and Environmental (timeouts, rate limits, context overflow)
  • View trends for your agents in the Signals view on Harness Runtime; drill from any trend into the sessions behind it
  • Flagged sessions become Evaluations scenarios in one click, with no manual test-data prep
  • Download flagged sessions to fine-tune your models or use as reward and preference data for reinforcement learning
  • Opt-in; PII scrubbed before any computation runs; traces and trace-derived evaluations stay within your DigitalOcean Team boundary and are never used to train shared or cross-customer models

Test the fix before it ships

Evaluations scores agents and models against a consistent bar. Simulations, new in Evaluations, tests any change across full multi-turn conversations before users see it.

Scoring and validation

Evaluations

Evaluate any candidate on your inference stack: Serverless Inference models, Dedicated Inference endpoints, imported BYOM models, and Inference Router policies

  • Eleven pre-built single-turn LLM-as-a-Judge metrics, from correctness, faithfulness, and toxicity to refusal appropriateness and prompt-injection resistance, plus multiple-choice accuracy and numeric-equivalence checks and custom rubrics you define
  • Multi-turn metrics for agents: user-goal completion, knowledge retention, conversation completeness, turn relevancy, tool-use accuracy, and agent policy adherence
  • Quality scores alongside TTFT, latency, throughput, and tokens per request in one dashboard
  • Save presets and re-run identically across model versions, so v1 vs. v2 is always apples to apples
  • Scenarios flagged by Signals land here directly, ready to run
  • Trigger evaluations via API, SDK, or MCP, on a schedule, on deployment, or from any agent workflow

New in Evaluations

Simulations (Public Preview)

Generate scenarios from Signals, plain-language descriptions, or your agent’s configuration

  • Weight scenario generation toward where production traffic already shows friction and what your change is most likely to affect
  • Run them against your candidate on Harness Runtime with your production tools and config, with mock tools for anything risky or costly
  • Play each scenario several times to catch intermittent failures, not just the happy path
  • Compare evaluation runs side by side, baseline against candidate, to see exactly what a change improved or regressed
  • Score every trajectory on Evaluations metrics to see exactly what improved and what regressed
  • Record every tool call so you can tell a reasoning failure from a tool-use failure
  • Validate anything from a prompt tweak to a fine-tuned or RL-trained model, and keep the scenarios that matter as regression tests

One loop, from production to validated change

Run.

Your models serve through Inference Engine; your agents run on Managed Agents. Nothing to instrument.

Observe.

Signals stitches turns into sessions, triages them, and identifies trends that you can drill into.

Convert.

Flagged sessions become evaluation scenarios in one click.

Simulate.

Simulations runs your changed model or agent through those scenarios as full conversations in an isolated sandbox, then grades each conversation on multi-turn metrics.

Ship.

Deploy the validated change. Signals keep watching. Scenarios worth keeping become regression tests.

Why teams choose DigitalOcean Learning Services

Grounded in production

Scenarios come from real sessions, and candidates run on the actual production harness, tools, and config. Real behavior, not a synthetic guess.

Insight becomes action

The same session that reveals a problem becomes the evaluation that validates the fix. No manual test-data prep.

Native, not bolted on

Runs on Managed Agents and Serverless Inference with nothing extra to instrument, whether you’re operating agents, serving models, or both. One console, one bill, one team boundary for your data.

FAQ

Improve your agents and models with evidence

Turn on Signals for an agent or model you're already running, and rehearse your next change in Simulations before your users see it.