# Customer tracing destinations

> Connect organization and agent traces to Braintrust, Langfuse, LangSmith and OpenTelemetry collectors with explicit privacy and routing controls.

Source: <https://everruns.com/docs/observability/destinations/>

Connect your own tracing backends from **Settings → Organization → Tracing**. Organization administrators manage destinations and routing. Members can inspect non-secret destination metadata and routing.

Self-hosted deployments must configure `SECRETS_ENCRYPTION_KEY` before creating connections. See [Environment variables](https://everruns.com/docs/sre/environment-variables/). Collector hosts must also be allowed by the deployment’s egress policy.

## Add a destination

1. Choose **Add destination** and give it a recognizable name.
2. Select **Braintrust**, **Langfuse**, **LangSmith**, or **OpenTelemetry / OTLP**. You can add multiple destinations using the same provider.
3. Enter an HTTPS endpoint. For Braintrust, enter the project UUID and API key. For OTLP, choose the authentication header your collector expects, or leave it empty for a collector that needs no authentication. Supported headers are `Authorization`, `X-API-Key`, and `Api-Key`. The exporter uses HTTP/protobuf and appends `/v1/traces` unless it is already present. For Langfuse, enter the project public key and secret key. Use the region’s full `/api/public/otel/v1/traces` HTTPS endpoint. Everruns supplies Basic authentication and the v4 ingestion header automatically. For LangSmith, enter a workspace-scoped API key, project name, and the full `/otel/v1/traces` endpoint for your region (self-hosted deployments may use `/api/v1/otel/v1/traces`). For agent-based LangSmith workspaces, use the environment’s `tracer_session_name` as the project name. Create the agent/environment in LangSmith first; Everruns does not provision it.
4. New destinations start with metadata only. After creation, use **Edit destination** to enable **Include messages and tool content** when your retention policy permits exporting inputs, outputs and tool arguments/results. **Include reasoning content** requires a separate opt-in.
5. Save, then use **Send test trace** from the destination menu. The test contains synthetic metadata. **Export accepted** means the receiver accepted the request, not that the provider has indexed it in its UI.

Credentials are encrypted and never returned by the API. Editing a destination leaves stored credentials intact unless you replace authentication. Changing the receiver requires new authentication settings. Endpoints cannot contain URL credentials, queries or fragments. Host egress policy can block private networks or disallowed hosts; customer exports require DNS pinning.

New destinations start **Unassigned**. Creating one does not export agent data.

Native Langfuse and LangSmith destinations use OTLP/HTTP protobuf with provider span kinds and session correlation, alongside GenAI/OpenInference model, usage, content and error attributes. No collector or process-wide environment variables are required. LangSmith supports either a project name for project-based workspaces, or a registered LangSmith agent ID with its local/development/staging/production environment. These are receiver destinations, independent of the Everruns agent that inherits or overrides organization routing. The two receiver modes are mutually exclusive; each destination has its own exporter and request-level routing headers, so batches do not mix destinations. Regional/self-hosted endpoints remain explicit: switching provider or endpoint requires entering replacement credentials. Provider UI indexing and cost estimation remain receiver-specific; test-trace acceptance is not a live UI verification. See the [Langfuse OTLP reference](https://langfuse.com/integrations/native/opentelemetry) and [LangSmith OTLP reference](https://docs.langchain.com/langsmith/trace-with-opentelemetry).

## Choose routing

Use **Edit defaults**, select destinations and **Save changes** to set organization defaults. From an agent’s **More → Tracing** drawer choose:

* **Use organization defaults**: use the organization’s current defaults.
* **Add to organization defaults**: send to defaults plus the selected destinations, deduplicated.
* **Use selected destinations**: send only to the selected destinations.
* **Turn off external tracing**: stop customer exports for this agent.

You can select up to eight defaults and eight destinations in an agent policy. Each organization can configure up to 32 destinations. Changes apply to new turns, including new turns in existing sessions. A running turn keeps its initial routing. Guest responders use their own agent policy; child sessions resolve their own policy. Personal Chat and sessions descended from it are excluded.

**Discard** abandons unsaved routing edits. **History** reviews saved routing; restores use revision checks. A stale Save or Undo requires reloading and reviewing the current configuration. Page-side Chat can draft routing for manual review; credentials and content-capture settings remain protected manual controls. Destination history restores its name and pause state while preserving current credentials, receiver, and content settings.

## Delivery and troubleshooting

Exports use independent, bounded queues and retries. A slow or failing receiver does not stop agent execution or other destinations. Delivery is best effort: queue overflow, exporter limits, process restart or a routing lookup failure can lose events. A queued turn-start is omitted if its organization or agent policy changed after the turn began; destinations configured later are also excluded. New consent never applies backward to delayed starts. There is no historical replay or guaranteed delivery. After an exporter restart, already-running turns are omitted rather than re-routed under newer settings. The table shows receiver acceptance, safe failure messages and destination queue drops. Global router drops also have a server metric, `everruns_customer_tracing_router_dropped`. Enabled destinations with delivery failures contribute an organization health issue.

**Pause destination** prevents subsequent sends, including queued retries, at the network boundary. Changing configuration or authentication also retires queued sends using the previous revision. An already in-flight request cannot be recalled. Remove a destination from all policies before deleting it; deletion leaves data already exported to the provider intact.

Deployment-wide [OpenTelemetry](https://everruns.com/docs/observability/opentelemetry/) and [Braintrust](https://everruns.com/docs/observability/braintrust/) configuration continues independently. Customer settings do not change platform exporters.