Skip to main content
Monitoring plugin · listing tai42/monitoring-langfuse

​
Install

​
Permissions

​
Provides

​
langfuse

Monitoring — Langfuse monitoring backend — trace/span emission and the observability read surface. The Langfuse monitoring backend writes tool-run and agent-turn traces to a Langfuse project — cloud or self-hosted — and the Studio reads them back through the same interface.

​
Enable it

manifest.yml

​
Configuration

The LANGFUSE_ env group. Create a project in Langfuse Cloud or a self-hosted instance and copy its key pair from the project settings.
Selecting monitoring_module without the three required keys raises at startup, naming all three — a monitoring backend that silently drops traces is worse than a server that will not boot. To run without monitoring, omit monitoring_module entirely; the runtime falls back to a built-in no-op.

​
Share one project between deployments

LANGFUSE_TRACING_ENVIRONMENT both stamps writes and scopes reads, so several deployments can share one Langfuse project by diverging on it — staging and production write into the same project and each reads only its own traces. Reading a trace by id is the one unscoped call, because trace ids are globally unique.

​
Quirks

  • The package pins the Langfuse SDK to a narrow range because it reaches into SDK internals for the read paths. Upgrading the Langfuse server is safe; changing the pinned SDK is not.
  • A self-hosted Langfuse is a standalone stack (its own Postgres, ClickHouse, Redis, and object store); wire the runtime to it with the four variables above.

​
See also

  • Observe — metrics, traces, and what the runtime emits.