Skip to main content
RAGLight 4 provides native Langfuse tracing through an optional adapter. The core remains dependency-free and no telemetry is sent unless a tracer is injected.

Install and configure

Configure the Langfuse SDK with its standard environment variables:

Classic RAG

The trace ID returned by RAGLight is mapped to the Langfuse trace context. Classic traces contain a root chain plus applicable reformulation, retrieval, reranking, and generation observations.

Agentic RAG

Pass the same tracer to the separate API:
Agentic traces include the root agent execution, each decision, and every tool call. Failed tools are marked as error observations while remaining available to the agent as recoverable results.

Short-lived processes

The SDK batches exports. Flush explicitly before a script, job, or test process exits:
Applications may inject their own object implementing the structural Tracer protocol. This is useful for tests or another observability backend and requires no RAGLight inheritance.