Schedule usage reports

Send a recurring digest of usage, cost, and performance.

Reports turn selected observability metrics into a recurring digest. Use them when a team needs a scheduled summary; use Metrics dashboards for interactive analysis and Monitors for threshold-based alerts.

Configure the schedule

  1. Turn on Usage report is active when the report is ready to run.
  2. Under Repeat on, select the weekdays that should receive the digest.
  3. Set the delivery time shown in the editor. Confirm the timezone displayed beside Time before saving.
Respan Reports editor showing an active weekday schedule, delivery time, included metrics, grouping dimensions, and top-results control.
The report editor combines the recurring schedule with the metrics and breakdowns included in the digest.

Choose the contents

The Include control selects the sections in the report. The current editor offers Spans, Errors, Users, Cost, Tokens, Latency, and Pulse.

Use Group by to break a metric down by API key, Model, Customer, or Prompt. Show top limits the number of results included for each selected group.

Choose the smallest set that answers the recipient’s recurring question. For example:

GoalSuggested contents
Daily reliability summarySpans, Errors, and Latency grouped by Model
Spend reviewCost and Tokens grouped by API key or Model
Customer usage digestSpans, Cost, and Tokens grouped by Customer
Prompt performance reviewErrors and Latency grouped by Prompt

A report summarizes selected metrics on its schedule. It does not replace a monitor: use a monitor when a threshold crossing should notify responders immediately.

Review activity

Open Activity to see changes such as creating, updating, turning on, or turning off the usage report. Use this history to confirm that a schedule change was recorded and to understand why delivery behavior changed.

Respan report Activity panel showing creation, update, enable, and disable events with actor details redacted.
Activity records configuration and enabled-state changes for the usage report.

The current editor and activity view do not document delivery retries, missed-run recovery, retention, or recipient permissions. Do not use a scheduled report as the only mechanism for incident paging or compliance delivery.