Skip to main content

Usage and Consumption

The /dashboard/usage screen consolidates the metered consumption of all the organization's customers: API events, messages sent, transactions processed, storage — any metric the catalog defines as "usage" and that is billed by consumption.

Consolidated view​

The main table groups consumption by product and by billing account, with:

  • Product (with its unit of measure — calls, events, messages, GB)
  • Customer / billing account
  • Quantity in the period
  • Last recorded event — with relative time
  • Estimated amount — projected charge for the next invoice

Filters​

  • Date range — defaults to the start of the current month through today.
  • Customer — combobox of billing accounts.
  • Show zeros — toggles whether accounts without consumption appear in the list.

Where the data comes from​

Usage events arrive through:

  1. Usage Records API — POST /v1/subscription_items/{id}/usage_records (Stripe-like pattern).
  2. usage-sync worker — runs every hour and aggregates external counters when configured.
  3. CSV import — for batch loads, via Imports.

Each usage record is linked to a SubscriptionItem with a metered product. At the cycle turnover, the invoice-generation worker turns the period's consumption into an invoice line.

Clearing​

Operators with permission can reset a customer's usage records (useful for test cases). The action is recorded in the Audit Log.

Screenshot​

Consolidated usage panel with consumption by product and customer