disk. Docker's default json-file logging does not rotate, so a long-running instance can fill the disk unless you configure log rotation.
Who it is forA developer whose agent gives odd answers and who cannot see which prompt, retrieval or tool call went wrong.
The problemWithout tracing, debugging an LLM app means print statements and guesswork.
The outcomeA local Langfuse instance showing each LLM call, retrieval step and agent action in your app.
What you need first
- Docker and Docker Compose for local self-hosting, or a Langfuse Cloud account
- The Python or JS/TS SDK, or a supported framework integration
- For production: a VM, Kubernetes with Helm, or Terraform on AWS, Azure or GCP
Steps
- Clone the repo with
git clone --depth=1 https://github.com/langfuse/langfuse.gitandcd langfuse - Start it with
docker compose up - Instrument your app with the Python or JS/TS SDK, or a drop-in integration such as OpenAI, Langchain or LlamaIndex
- Open the Langfuse UI and inspect the traces for a request that went wrong
- Configure Docker log rotation, since the default json-file driver does not rotate logs
Prompt for your agent
Self-host langfuse/langfuse locally with Docker Compose, then add tracing to my <app> using the <OpenAI or Langchain> integration. Send a few test requests and show me the trace for the slowest one.
Caveat. The local Docker Compose setup is for trying it out; the README recommends Kubernetes with Helm for production.
Use this in your AI agent
Ask your agent
Using the Deduped MCP, get the setup steps for langfuse/langfuse and "Self-host LLM tracing in five minutes"
Add Deduped to Claude Code once
claude mcp add --transport http deduped https://dedupedai.com/mcp
Every Monday: the 5 hottest repos and exactly how to use them. Free, one email a week, unsubscribe anytime.
Get them freeShare: X LinkedIn Hacker News Email Copy link
Third-party repos we don't own. AI-written use cases can be wrong. Disclaimer