> ## Documentation Index
> Fetch the complete documentation index at: https://allhandsai-vertex-agent-server-docs.mintlify.site/llms.txt
> Use this file to discover all available pages before exploring further.
# Analytics
> Deploy Laminar for trace analysis in OpenHands Enterprise.
This guide walks you through enabling Laminar in OpenHands Enterprise (OHE) so conversations automatically send traces for observability and analysis.
For SDK-level tracing concepts, OTEL environment variables, and non-Laminar backends, see [Observability & Tracing](/sdk/guides/observability).
## Who This Is For
This guide is for users who want to deploy Laminar alongside OpenHands Enterprise and inspect traces from Enterprise conversations.
## Why Laminar in OHE?
Laminar helps you understand what your OpenHands deployment is doing in production:
* Inspect prompts, tool calls, answers, and nested agent behavior in Laminar's [trace views](https://laminar.sh/docs/platform/viewing-traces).
* Use [session replay for browser agents](https://laminar.sh/docs/tracing/browser-agent-observability) when conversations drive browser automation.
* Define [signals](https://laminar.sh/docs/signals/introduction) to classify failures, measure outcomes, and monitor recurring patterns across many traces.
For more information on evaluating skills, see [Evaluating Agent Skills](https://www.openhands.dev/blog/evaluating-agent-skills).
## Prerequisites
Before you begin, complete the [Quick Start guide](/enterprise/quick-start).
## Enable Analytics
You should see an **Analytics Configuration** section on the application configuration page.
Check the **Enable Analytics** box to have the installer set up and configure Laminar for analytics.
## Deploy
OpenHands will begin deploying. You can expect the deployment status to transition from **Missing** to **Unavailable** to **Ready**. This typically takes 10-15 minutes.
Click **Details** next to the deployment status to monitor individual resources. Resources shown in orange are still deploying, so wait until all resources are ready.
## Access the Laminar UI
Once the deployment status shows **Ready**, navigate to `https://analytics.app.`.
Click the **Continue with Keycloak** button:
If you want more background on Laminar Cloud versus self-hosting outside OHE, see Laminar's official [hosting options](https://laminar.sh/docs/hosting-options).
## Create a Laminar Project
Create a project in the Laminar UI:
Once a project has been created, Laminar is ready to listen for traces.
## Create an Ingest-Only API Key
Always use ingest-only API keys when deploying OHE.
Ingest-only keys are recommended because OHE only needs permission to write traces. They cannot be used to read trace data.
## Set the Laminar Project API Key
Set the ingest-only key as the **Laminar Project API Key** in the Admin Console configuration. This is the same `LMNR_PROJECT_API_KEY` described in the [SDK observability guide](/sdk/guides/observability).
Click **Save config**.
## Forward `LMNR_` and `LLM_` Environment Variables
In OHE, environment variables whose names start with `LMNR_` or `LLM_` are automatically forwarded to the SDK runtime. This lets you configure Laminar ingestion settings and the LLM settings used for Laminar-backed workflows from the Admin Console.
For example, you can point the runtime at the managed Laminar endpoint and use an ingest-only project key:
```yaml theme={null}
LMNR_BASE_URL: "https://laminar-api."
# Ingest-only API key, not a read-capable secret:
LMNR_PROJECT_API_KEY: ""
LMNR_FORCE_HTTP: "true"
```
You can also control which LLM Laminar uses for its AI features — chat-with-trace, SQL-with-AI, and [signals](https://laminar.sh/docs/signals/introduction) — by forwarding the standard `LLM_*` variables:
```yaml theme={null}
LLM_PROVIDER: "openai"
LLM_BASE_URL: "https://llm-proxy."
LLM_MODEL_SMALL: "gpt-5.4-mini"
LLM_MODEL_MEDIUM: "gpt-5.4-mini"
LLM_MODEL_LARGE: "gpt-5.5"
```
`LLM_PROVIDER` accepts `gemini` (Laminar's default), `openai`, or `bedrock`, and `LLM_MODEL_SMALL` / `LLM_MODEL_MEDIUM` / `LLM_MODEL_LARGE` are optional per-tier model overrides. Set `LLM_PROVIDER` to `openai` whenever you point `LLM_BASE_URL` at an OpenAI-compatible gateway (for example LiteLLM, OpenRouter, or vLLM), not just the public OpenAI API.
For the full set of supported values, see Laminar's official [self-hosting configuration reference](https://laminar.sh/docs/self-hosting/configuration).
## Deploy Updated Configuration
Deploy the configuration change after setting the Laminar Project API Key in the Admin Console.
Wait for the deployment to complete.
## Start a Conversation
Navigate to the OpenHands UI at `https://app.`. Start a new conversation and try a prompt.
Your conversations will now automatically send traces to Laminar.
## What to Do Next in Laminar
Once traces are flowing, use Laminar's official docs to go deeper:
* [Viewing Traces](https://laminar.sh/docs/platform/viewing-traces) to inspect a single conversation in transcript, tree, or timeline views.
* [Signals](https://laminar.sh/docs/signals/introduction) to extract structured outcomes or failure modes across many traces.
* [Session replay for browser agents](https://laminar.sh/docs/tracing/browser-agent-observability) to debug browser-based automations.
* [Observability for OpenHands Software Agent SDK](https://laminar.sh/docs/tracing/integrations/openhands-sdk) for the OpenHands-specific tracing model.
## Next Steps
Learn the full OpenHands tracing model, OTEL configuration options, and non-Laminar backends.
Get more reliable traces by improving the prompts you give your agents.
Reach out to the OpenHands team for deployment assistance or questions.