PLTF-2905: Document enabling Laminar Signals in OHE

enterprise/analytics.mdx

@@ -16,7 +16,7 @@
 
 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.
 
@@ -48,11 +48,11 @@
 
 Once the deployment status shows **Ready**, navigate to `https://analytics.app.<your-base-domain>`.
 
 Click the **Continue with Keycloak** button:
 
 ![Laminar Keycloak Auth](./images/laminar-keycloak-auth.png)
 
 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
 
@@ -103,10 +103,49 @@
 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).
 
+## Enable Signals
+
+[Signals](https://laminar.sh/docs/signals/introduction) extract structured events from your traces using the same LLM provider configuration described above. They are enabled by default once an LLM key is configured, so enabling them is mostly a matter of pointing Laminar at a working LLM.
+
+1. **Configure an LLM provider and key.** Set `LLM_PROVIDER` and `LLM_API_KEY` (and `LLM_BASE_URL` when you use an OpenAI-compatible gateway). Signal extraction runs in the `app-server-consumer` component, so keep `llmProvider` consistent across the `frontend`, `appServer`, and `appServerConsumer` Laminar components:
+
+   ```yaml
+   frontend:
+     env:
+       llmProvider: "openai"
+   appServer:
+     env:
+       llmProvider: "openai"
+   appServerConsumer:
+     env:
+       llmProvider: "openai"
+   ```
+
+2. **Make sure Signals are turned on.** Signals are on by default once an LLM key is set. You can set the flag explicitly for clarity (and use `"false"` to turn them off):
+
+   ```yaml
+   frontend:
+     env:
+       signalsEnabled: "true"
+   ```
+
+3. **Provide the key the frontend feature flag checks.** Depending on your Laminar version, the frontend gates the **Signals** tab on a Gemini key. If you are not using the `gemini` provider, also set `GOOGLE_GENERATIVE_AI_API_KEY` (it can be the same key you use for `LLM_API_KEY`) so the tab appears:
+
+   ```yaml
+   frontend:
+     env:
+       signalsEnabled: "true"
+     extraEnv:
+       - name: GOOGLE_GENERATIVE_AI_API_KEY
+         value: "<your-llm-api-key>"
+   ```
+
+After saving and redeploying, the **Signals** tab appears in the Laminar UI. See Laminar's official [Signals configuration](https://laminar.sh/docs/self-hosting/configuration#signals) and [Signals guide](https://laminar.sh/docs/signals/introduction) for details.
+
 ## Deploy Updated Configuration
 
 Deploy the configuration change after setting the Laminar Project API Key in the Admin Console.
@@ -133,11 +172,11 @@
 
 ## 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