Usage Event Log - Custral Docs

Overview

Usage Event Log lists the individual events recorded against a usage module, newest first. One row is one event, not one customer. Placed on a record page it scopes to that record, so a customer’s page shows only their own events.

Configuration

Setting	What it does
Usage Module	The usage module whose events to display. Required.
Record Role	On a record page, filter events to that record’s role: `product` or `customer`. Leave empty for a global view of every event in the module.

What each row shows

Column	Contents
Product Record	The product side of the event.
Customer Record	The customer side of the event.
Quantity	How many units the event recorded.
Occurred At	When it happened, in your local time.

Each row carries a delete action, and the block has a Log Event button for recording one by hand. Most events arrive through the ingest endpoint instead; see Usage tracking.

Use cases

Auditing what a customer was billed for, on their own record page.
Checking that a new ingest integration is landing events, on a global view.
Correcting a bad event by deleting it and logging a replacement.

Troubleshooting

Symptom	Likely cause	What to check
”No usage module configured”	The block has no module selected	Set Usage Module, or use Configure Module in the empty state to create one.
”No usage events recorded yet”	Nothing has been sent to this module, or none of it matches the scoped record	Confirm events are landing, and that the open record is the module’s product or customer object.
Every record shows every event	Record Role is empty, so the block is global	Set the role to `product` or `customer`.
Events land on the wrong records	The module is matching your own keys against the wrong property	Check the module’s identifier property for that side. See Usage tracking.

See also

Usage Stat: these events as a single number.
Usage tracking: modules, events, and the ingest endpoint.
Usage property: a rolled-up total on the record itself.