Skip to main content
Analytics adds up activity across every session in your organization: what agents did, what it cost, how long sessions took to finish, and how fast sandboxes started. Use it to spot a failing tool, a costly model, or a slow environment, then open the sessions behind the number. For one session or one tree, see Usage and cost. The samples assume the rl client from Client setup.

Before you begin

  • Any role that can read Managed Agents can read analytics. See Organizations and roles.
  • Figures cover your own organization.

Metric families

Each request reads one family.

Read analytics

  1. In the sidebar, click Analytics.
  2. Choose a view: Usage, Completions, Environments, or Quality.
  3. Choose a time range from Last 24 hours to Last year. The default is Last 7 days.
  4. Read the chart and the Agents, Tools, and Models tables below it. The header shows how current the figures are.
Money is in micro-USD: 1000000 is one US dollar. Every figure set has the same fields; a family fills the ones it measures and reports zero for the rest.

Choose the window and filters

Read the response

  • totals is the whole window as one figure set. series is one point per bucket, oldest first; buckets with no activity are left out, so fill them with zero when you chart. breakdowns are the family’s default groupings, each with rows ranked by the family’s main measure and capped by limit.
  • Rows carry a value to pass back as a filter, and a readable label for agents, agent versions, and environments.
  • Percentiles (p50_ms, p90_ms, p95_ms) are approximate. duration_samples says how many measurements they come from. Counters and sums are exact. Stacked series_groups leave percentiles out.
  • Freshness. as_of is how current the figures are, and lag_seconds is how far behind now that is. A steady lag under a minute is normal; activity after as_of shows up in a later read.
What each family counts. sessions counts sessions once, in the bucket they started in. In managed_agent_completion, it counts root sessions by when they first finished successfully, and session_completion_ms divided by sessions is the mean time to finish. turns is filled only by managed_agent_turn. environment_startup_ms sums startup time over successful startups only.

Use analytics well

  • Find what’s failing. Read managed_agent_usage with series_group_by=tool_name and compare tool_failed with tool_calls.
  • Find where money goes. Break down by model and by executing_agent_id, then open that agent’s sessions in Usage and cost.
  • Watch environments. A rising environment_failed or p95_ms in managed_agent_environment points at a setup script or a machine type.
  • Compare versions. Filter by executing_agent_version_id before and after a change to an agent.

What can go wrong

For every error code, see Errors.

Limits

See Limits for every other limit.

Next steps

Usage and cost

Read one session’s or one tree’s cost.

Evaluations

Score sessions and chart quality over time.

Environments

Fix slow or failing sandbox startups.

Sessions

Open the sessions behind a number.