Skip to main content
Telara

Integrations / LangSmith (LangChain / LangGraph)

LangSmith (LangChain / LangGraph) logo

LangSmith (LangChain / LangGraph)

LangSmith observability — per-run traces for LangChain/LangGraph agents (latency, tokens, cost, status). Pull connector for teams already tracing to LangSmith; teams without LangSmith use the Telara OTLP instrumentation lane instead.

API key
Spend

What Telara does

Capability matrix

Indexes NoTracks spend YesDiscovers shadow AI NoRuns actions NoReal-time events No

Before you connect

Prerequisites

A LangSmith workspace you can administer.

Vendor setup

Get the credential

1
Create an API key
In LangSmith, open Settings → API Keys. Create a workspace-scoped key.
2
Paste in Telara
Settings → Integrations → LangSmith. Paste the key and the workspace id.

In Telara

Connect in Telara

API key

LangSmith API key (Settings → API Keys). Workspace-scoped keys pull only that workspace's runs. Store the LangSmith workspace ID as workspace_id so Telara can send X-Tenant-Id on the live /runs/query API. Available on all LangSmith plans.

In Telara, open Settings → Integrations, choose this connector, and paste the key into the fields Telara shows.

Fields Telara asks for
  • API key
  • Workspace Id

Spend

What gets measured

Resolution: Per run.

Attribution: Matched to people by email.

How far back vendor history goes is not published uniformly for this connector.

  • input_tokens
    tokens
  • output_tokens
    tokens
  • framework_runs
    count

Sync

Freshness & sync

Spend connectors refresh on the vendor pull cadence declared in the catalog. Indexing lag is not published for this connector.

Data handling

Permissions & data handling

Telara has not published a permission list for this connector yet. Treat the vendor consent screen as the source of truth until this page lists scopes.

This catalog entry does not declare extra semantic-search exclusions.

After connect

Verify it worked

After you save, Telara runs a read-only check against the account. The integration shows as connected when that check succeeds.

Honesty

Known limitations

Personal keys that are not scoped to the workspace Telara should see will under-count runs.
This is not the LangSmith webhook connector, and not LangChain SDK telemetry.