Integration

Connect Langfuse to Rootline

Rootline reads the traces you already send to Langfuse. No code changes: paste your host and an API key pair in Settings.

RootlinePublished

Short answer

Create a Langfuse API key pair (a Viewer, read-only key is enough), then paste the host, public key and secret key in Rootline under Settings → Langfuse connection. Rootline imports the last 30 days of traces and from then on fetches only new observations. No code changes in your agent.

What you need

  • A Langfuse project on Langfuse Cloud (EU, US, Japan or HIPAA region), or self-hosted Langfuse v4 reachable over https on a public address.
  • Permission to create API keys in that project (the Owner or Admin role in Langfuse).
  • A free Rootline account.

Set up

  1. Create a key pair in Langfuse. Project Settings → API Keys → Create new API keys. Under Permissions, choose Viewer for read-only access. Copy the public key (pk-lf-…) and the secret key (sk-lf-…).
  2. Open Rootline Settings. Sign up or log in, then go to Settings → Langfuse connection.
  3. Paste the host and keys. Use the base URL of your region or instance, without /api/public.
  4. Connect & import. Rootline checks the keys by importing the last 30 days. The keys are saved only if that import succeeds.
  5. Look at your failures. Failed and suspicious runs appear with the failing step highlighted. AI explanations follow within a few minutes.
host        https://cloud.langfuse.com        # EU; US: https://us.cloud.langfuse.compublic key  pk-lf-…secret key  sk-lf-…                           # encrypted before storage

Which hosts work

Rootline calls the host you enter with your API keys, so it only accepts hosts that are safe to call from its servers:

HostAccepted?
https://cloud.langfuse.com (EU), https://us.cloud.langfuse.com, https://jp.cloud.langfuse.com, https://hipaa.cloud.langfuse.comYes
Self-hosted, e.g. https://langfuse.example.com or https://example.com/langfuseYes, if every address the name resolves to is public
http://… (no TLS)No: https only (an old http://cloud.langfuse.com entry is upgraded to https)
Private, loopback, link-local or reserved addresses: localhost, 10.x, 192.168.x, 169.254.169.254, fd00::/8 and similarNo
URLs with a user name or password, a query string or a fragmentNo

The address is checked when you connect and again on every request Rootline makes, and Rootline connects only to the address it checked. Redirects are not followed: if your instance redirects, enter the final https URL.

What Rootline reads

  • One endpoint: GET /api/public/v2/observations (Observations API v2), with HTTP Basic auth. Rootline never creates, changes or deletes anything in Langfuse.
  • First import: the last 30 days, up to 20,000 observations.
  • Later syncs: incremental, from a stored cursor with a 5-minute overlap so late-arriving observations aren't missed.
  • From each observation: type, name, timing, level and status message, input and output, model and usage, cost, user ID, tags and metadata. Runs are rebuilt by grouping observations by trace.
  • Feature and customer: a feature metadata key or a feature:<name> tag sets the feature, and the Langfuse user ID is the customer. They are used to group issues and, on Team, for cost per customer and feature.

Keys and data

  • The secret key is encrypted before it is stored. You can revoke the key pair in Langfuse at any time; syncing then stops with an error in Settings.
  • Imported trace data, explanations and alert records are deleted automatically after 90 days.
  • For AI explanations, only a truncated, redacted excerpt of each failed run (about 2,000 characters) is sent to an AI provider. You can turn AI explanations off in Settings and get rule-based explanations instead. See the privacy policy.

Disconnect

Settings → Langfuse connection → Disconnect deletes the stored keys and every run imported from Langfuse. Runs sent over OpenTelemetry are kept.

Troubleshooting

MessageLikely cause
401 UnauthorizedWrong key pair, keys from another project, or the wrong region (an EU key against the US host). Expired keys also return 401.
"The Langfuse host must use https://"The host starts with http://. Use the https URL.
"points to a private or reserved address"The host resolves to an internal address. Rootline can only reach instances on public addresses.
"redirected"The URL you entered redirects elsewhere. Enter the final https URL of your Langfuse instance.
An HTTP error such as 404 on a self-hosted instanceObservations API v2 needs self-hosted Langfuse v4. Older versions only have the v1 endpoints.
Imported 0 runsNo traces in the last 30 days in that project, or the key belongs to a different project.

Official documentation

Connect your Langfuse traces

Free plan, no credit card. The first import covers the last 30 days.

Start debugging free creates a free account, no card. Then open Settings → Langfuse connection and paste your project's host and API keys. No code changes.