Skip to main content
Telara

Integrations / Langfuse

Langfuse logo

Langfuse

Langfuse LLM observability — pull per-trace spend, latency, and model usage via the Langfuse public API. Zero-code alternative to OTLP instrumentation for teams already tracing to Langfuse.

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 Langfuse project (Cloud or self-hosted) Telara can reach.
Permission to view that project’s API keys.

Vendor setup

Get the credential

1
Copy both keys
In Langfuse, open Project Settings → API Keys. Copy the public key and the secret key.
2
Paste in Telara
Settings → Integrations → Langfuse. Telara uses them as a username/password pair. Set the host if you are self-hosted.

In Telara

Connect in Telara

API key

Langfuse public key and secret key (Project Settings → API Keys). Credentials are sent as HTTP Basic auth: username=public_key, password=secret_key. Available on all Langfuse plans including the self-hosted OSS edition.

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

Fields Telara asks for
  • Public Key
  • Secret Key

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

Public key alone is not enough.
A key from a different project will connect then show the wrong traces.