docs: add LMNR_HTTP_PORT and LMNR_GRPC_PORT env vars for self-hosted Laminar

sdk/guides/observability.mdx

@@ -1,6 +1,6 @@
 ---
 title: Observability & Tracing
 description: Enable OpenTelemetry tracing to monitor and debug your agent's execution with tools like Laminar, MLflow, Honeycomb, or any OTLP-compatible backend.
 ---
 
 > A full setup example is available [here](#example:-full-setup)!
@@ -12,7 +12,7 @@
 - **[Laminar](https://laminar.sh/)** - AI-focused observability with browser session replay support
 - **[MLflow](https://mlflow.org/)** - Open-source AI platform with tracing, evaluation, and LLM governance
 - **[Honeycomb](https://www.honeycomb.io/)** - High-performance distributed tracing
 - **Any OTLP-compatible backend** - Including Jaeger, Datadog, New Relic, and more
 
 The SDK automatically traces:
 - Agent execution steps
@@ -36,6 +36,14 @@
 
 That's it! Run your agent code normally and traces will be sent to Laminar automatically.
 
+For **self-hosted Laminar** deployments, you can also configure custom ports:
+
+```bash icon="terminal" wrap
+export LMNR_PROJECT_API_KEY="your-laminar-api-key"
+export LMNR_HTTP_PORT=8000
+export LMNR_GRPC_PORT=8001
+```
+
 ### Using OpenTelemetry (OTLP) Backends
 
 For OpenTelemetry (OTLP) compatible backends, set the following environment variables:
@@ -125,6 +133,8 @@
 | Variable | Description | Example |
 |----------|-------------|---------|
 | `LMNR_PROJECT_API_KEY` | Laminar project API key | `your-laminar-api-key` |
+| `LMNR_HTTP_PORT` | HTTP port for self-hosted Laminar | `8000` |
+| `LMNR_GRPC_PORT` | gRPC port for self-hosted Laminar | `8001` |
 | `OTEL_EXPORTER_OTLP_TRACES_ENDPOINT` | Full OTLP traces endpoint URL | `https://api.honeycomb.io:443/v1/traces` |
 | `OTEL_EXPORTER_OTLP_ENDPOINT` | Base OTLP endpoint (traces path appended) | `http://localhost:4317` |
 | `OTEL_ENDPOINT` | Short form endpoint | `http://localhost:4317` |
@@ -149,8 +159,8 @@
 
 The SDK supports both HTTP and gRPC protocols:
 
 - **`http/protobuf`** or **`otlp_http`** - HTTP with protobuf encoding (recommended for most backends)
 - **`grpc`** or **`otlp_grpc`** - gRPC with protobuf encoding (use only if your backend supports gRPC)
 
 ## Platform-Specific Configuration
 
@@ -164,20 +174,28 @@
 export LMNR_PROJECT_API_KEY="your-laminar-api-key"
 ```
 
+**Self-Hosted Laminar**: If you are running a self-hosted Laminar instance, you can configure the HTTP and gRPC ports via environment variables:
+
+```bash icon="terminal" wrap
+export LMNR_PROJECT_API_KEY="your-laminar-api-key"
+export LMNR_HTTP_PORT=8000
+export LMNR_GRPC_PORT=8001
+```
+
 **Browser Session Replay**: When using Laminar with browser-use tools, session replays are automatically captured, allowing you to see exactly what the browser automation did.
 
 ### MLflow Setup
 
 [MLflow](https://mlflow.org/) is an open-source AI platform that accepts OpenTelemetry traces out of the box, alongside evaluation and LLM governance capabilities.
 
 1. Start your MLflow tracking server:
 
 ```bash icon="terminal" wrap
 uvx mlflow server
 ```
 
 <Note>
 For other deployment options (pip, Docker Compose, etc.), see [Set Up MLflow Server](https://mlflow.org/docs/latest/genai/getting-started/connect-environment/).
 </Note>
 
 2. Configure the environment variables:
@@ -188,7 +206,7 @@
 export OTEL_EXPORTER_OTLP_TRACES_PROTOCOL="http/protobuf"
 ```
 
 Navigate to the MLflow UI (e.g., `http://localhost:5000`), select the experiment, and open the **Traces** tab to view the recorded traces.
 
 ### Honeycomb Setup
 
@@ -310,7 +328,7 @@
 
 **Solutions**:
 - Tracing has minimal overhead when properly configured
 - Disable tracing in development by unsetting environment variables
 - Use asynchronous exporters (default in most OTLP configurations)
 
 ## Example: Full Setup
@@ -374,5 +392,5 @@
 ## Next Steps
 
 - **[Metrics Tracking](/sdk/guides/metrics)** - Monitor token usage and costs alongside traces
 - **[LLM Registry](/sdk/guides/llm-registry)** - Track multiple LLMs used in your application
 - **[Security](/sdk/guides/security)** - Add security validation to your traced agent executions