# Verify it landed

Confirm your first session arrived in the Brizz dashboard, and what to do if it didn't.

You ran the code. Did the session make it into Brizz? This page closes that loop.

## Where to look

1. Open the Brizz dashboard and select your tenant.
2. Go to **Sessions** in the sidebar.
3. Look for a session with the ID you passed to `start_session` / `withSessionId` (e.g. `session-123`).

Click the session to drill in. You should see:

- The agent's input and final output at the top.
- A timeline of spans — every LLM call, tool call, and any events you emitted.
- Token counts, latency, and the raw request/response for each LLM span.

If you instrumented with one of the supported frameworks (LangChain, Vercel AI SDK, Agno, Strands, LiveKit Agents), the framework's own structure (chains, tools, agents) shows up natively in the timeline — you don't need to add spans by hand.

## Nothing showed up?

Run through this checklist before anything else:

- **API key is set.** `BRIZZ_API_KEY` is in the environment your app actually runs with — not just your shell. Print it from inside the app if unsure.
- **Initialization runs first.** `Brizz.initialize()` must execute *before* any AI library is imported.
- **Server-side only.** The SDK is meant to run on a trusted server. If you're trying to send telemetry from a browser, use [`@brizz/browser`](/docs/sdks/browser.md) instead.
- **Wait a few seconds.** Spans are batched. Refresh the Sessions page after ~5–10 seconds.
- **Check service filter.** The Sessions page may be filtered to a specific `service_name` from a previous look. The name you passed as `app_name` / `appName` is what appears here.

Still not seeing data? Head to [Troubleshooting](/docs/help/troubleshooting.md) — it covers the most common ingestion failures with fixes.

## See also

- [Next steps](/docs/get-started/next-steps.md) — what to instrument next now that the pipeline works.
- [Sessions (in the dashboard)](/docs/platform/sessions.md) — how to read the session view in depth.
- [Troubleshooting](/docs/help/troubleshooting.md) — initialization order, 401s, and more.