Skip to main content
The Langfuse resource exposes LLM observability data (traces, observations, prompts, datasets, scores) as a virtual filesystem mounted at some prefix such as /langfuse/. For credential setup, see Langfuse Setup.

Config

Filesystem Layout

Example:

Traces

/langfuse/traces/ lists recent traces (capped at default_trace_limit). Each trace is a .json file containing the full trace object with nested observations (spans, generations, events).

Sessions

/langfuse/sessions/ groups traces by session ID. Each session directory contains trace .json files belonging to that session.

Prompts

/langfuse/prompts/ lists prompt names as directories. Each prompt directory contains version files (1.json, 2.json, etc.) with the prompt content and metadata.

Datasets

/langfuse/datasets/ lists dataset names as directories. Each contains items.jsonl (dataset items) and runs/ with run results.

Smart Commands

grep at different scopes

At directory scope, the resource uses Langfuse’s filter API instead of downloading data:
  • traces/: filters by trace name, user ID, or tags
  • sessions/: filters by session listing
  • prompts/: filters by prompt name

head / tail

head and tail on traces/ use Langfuse API pagination with sort order instead of downloading all traces:

Limits

Cache

The Langfuse resource uses IndexCacheStore (same as other resources). Index entries store trace IDs, session IDs, and prompt names.

Example

Shell Commands