# Events

Browse and search the events your agent emitted — custom events and log records, with their body and attributes, and a link to the session where present.

The **Events** page is where you check what your instrumentation actually sent. Everything you emit with [custom events](/docs/instrument/custom-events.md), plus log records your agent produced, lands here.

## What it is

A flat, searchable list of one service's event stream — what you want when you're verifying instrumentation rather than reading a conversation. [Sessions](/docs/platform/sessions.md) shows the same events in conversation context.

## How it's populated

Directly from your telemetry, with no configuration and no analysis step in between. Arrival is asynchronous, so allow a short delay before concluding something is missing.

## How to read it in the dashboard

Pick a service first; the page is empty until you do.

- **Search by event name** — also rescopes both charts. Log records with no event name stay under an empty name and won't match.
- **Stats bar** — total events and *unique* event names. The unique count should be small; a jump usually means a dynamic value got baked into a name.
- **Events over time** — volume per bucket, narrowed to the searched name.
- **Event distribution** — the **top five** names, with percentages over just those five.
- **Event table** — timestamp, name, and session id. Sorting applies to the current page. Expand a row for the parsed body properties and the event's own attributes; a plain-text body has nothing to parse, and resource attributes aren't shown. Session id is optional, so some rows have no session to open.

## How to act on it

1. **Verify new instrumentation here first.** After adding a `record_event` call, search for its name — but check the service, date range, and name filter before concluding it never arrived.
2. **Watch the unique-event count.** Ids or timestamps interpolated into a name show up as runaway cardinality and make the event useless to aggregate on.
3. **Check attributes before building on them.** Confirm names and value shapes, then use the supported ones as [session filters](/docs/platform/sessions.md). Events aren't a [custom charts](/docs/platform/custom-charts.md) data source.

## Availability

On by default. If **Events** isn't in your navigation, [contact us](mailto:support@brizz.ai).

## See also

- [Custom events](/docs/instrument/custom-events.md) — how to emit events, and the naming conventions to follow.
- [Services & configuration](/docs/admin/services-and-configuration.md) — the per-service Events tab, where events map to Brizz system events.
- [Sessions](/docs/platform/sessions.md) — session-linked events in conversation context.