# Glossary

Alphabetical reference for terms used throughout the Brizz docs.

Quick definitions for every term that shows up across the docs. For a longer narrative of how these fit together, see [Core concepts](/docs/introduction/concepts.md).

## Adapter

A small SDK package that adds native span shapes for a specific framework (LangChain, Vercel AI SDK, Agno, Strands). See [Choose your SDK](/docs/sdks.md).

## Attribute

A key/value pair set on a span or event. Attributes are flat (string/number/boolean), filterable in the dashboard, and intended for high-cardinality querying.

## Body

The free-form JSON payload of an event. Use it for comments, larger blobs, and context that doesn't need to be filterable.

## Custom evaluator

A rule you define that runs against conversation data and writes an [issue](#issue) when it matches. Rules can be regex, classifier output, or LLM-as-judge.

## DSN

A single-paste credential bundling bearer token, endpoint, and service name. **Server DSN** (`brizz-ing-s-…`) is for backend SDKs; **Client DSN** (`brizz-ing-c-…`) is safe to ship in browser bundles.

## Event

A discrete signal emitted from your code — a business outcome, a milestone, a feedback action. Distinct from an LLM call. See [Custom events](/docs/instrument/custom-events.md).

## External metric

A [metric](#metric) *you* report rather than one Brizz computes — an eval score, a customer rating, a latency your own system measured. See [External metrics](/docs/platform/external-metrics.md).

## Intent

A semantic cluster of similar user prompts — "cancel my subscription," "stop auto-renew," and "turn off billing" collapse into one **Cancellation** intent. See [User intents](/docs/platform/user-intents.md).

## Issue

A deduplicated problem — one row per underlying issue, with frequency, first/last seen, and affected users. Carries an issue type and a priority. See [Issues](/docs/platform/issues.md).

## Journey

An aggregated path through your agent — a sequence many sessions follow. See [User journeys](/docs/platform/user-journeys.md).

## Maturation / matured

A [session](#session) or [trace](#trace) **matures** once it has been idle longer than its maturation window — a few minutes of quiet. Brizz reads that gap as the conversation being finished and runs its analysis pass, which is what materializes the transcript and produces metrics and [issues](#issue). A session can mature more than once if the user comes back after a gap; each pass increments its `maturation_count`. See [Outbound webhooks](/docs/api/webhooks.md).

## MCP (Model Context Protocol)

An open protocol for agents and tools to talk to each other. Brizz uses MCP in two directions: [auto-instrument an MCP server you run](/docs/sdks/mcp.md), and [expose Brizz as an MCP server](/docs/integrations/mcp-server/overview.md) so AI agents can query it.

## Metric

A number scored against a session — a quality rating, a latency, a cost. Where an [event](#event) says *what happened*, a metric says *how well it went*. Brizz computes some itself; the ones you report are [external metrics](#external-metric).

## OpenTelemetry / OTel

The open standard Brizz's SDK speaks. Spans, traces, and attributes follow OTel conventions, which means raw OTel exporters can also send data to Brizz.

## PII

Personally Identifiable Information — emails, phone numbers, SSNs, etc. Brizz includes built-in masking; see [PII & privacy](/docs/instrument/pii-and-privacy.md).

## Polarity

Which direction is good for a [metric](#metric). `positive` means a higher value is better (a quality score); `negative` means a higher value is worse (a hallucination rate). It's what lets Brizz colour a gauge without being told twice.

## Session

A logical conversation thread that groups multiple traces. The session ID is whatever you set in `start_session` / `withSessionId`. See [Sessions (instrumentation)](/docs/instrument/sessions.md) and [Sessions (in the dashboard)](/docs/platform/sessions.md).

## Span

One step inside a trace — an LLM call, a tool invocation, a function execution. Traces are trees of spans.

## SSO

Single Sign-On. Brizz supports SAML 2.0 IdPs; see [SSO (JumpCloud)](/docs/admin/sso-jumpcloud.md).

## System event

A built-in event type in the dashboard (e.g., **Positive Feedback**, **Negative Feedback**). Map your custom event names to system events in **Organization Settings → Event** so filters and charts pick them up.

## Tenant

An isolated workspace within Brizz. Every user belongs to one or more tenants; data never crosses tenants. Sometimes called an *organization*.

## Trace

The record of one end-to-end operation through your agent — one user message and the chain of LLM/tool calls it triggered. A trace is a tree of [spans](#span).

## User

The person interacting with your agent. Attach `user_id` (and optionally name/email) to a session to unlock user-level analytics. See [Identify users](/docs/instrument/identify-users.md).

## Webhook

An HTTP callback between Brizz and another system. Brizz has both directions, and they're configured separately:

- **Outbound** — Brizz calls an endpoint you own when a session or trace [matures](#maturation--matured). Configured per service, signed, and retried. See [Outbound webhooks](/docs/api/webhooks.md).
- **Inbound** — an external system such as [Segment](/docs/integrations/segment.md) pushes events into Brizz at a URL Brizz provides. Configured per integration.

## See also

- [Core concepts](/docs/introduction/concepts.md) — the narrative version of this page.
- [Troubleshooting](/docs/help/troubleshooting.md) — when something's not working.