Building with Langfuse
A 11-part guide. Start at Part 1, or jump to any part below.
The parts
- The Ticket You Cannot Reconstruct Is Why You Need Langfuse
- Langfuse Traces Are a Typed Tree, Not a Folder of Logs
- Your Trace Tree Is the API Your Evaluators Will Call
- Your Langfuse Trace Has No Customer. That Is Why You Cannot Query It.
- Langfuse Does Not Run Your Agent. It Wraps the One You Already Have.
- Stop Shipping Prompt Wording in a Pull Request
- You Changed the Prompt Without a Deploy. You Still Cannot Tell If the Reply Is Any Good.
- The Playground Looked Fine. That Is Not a Langfuse Experiment.
- One Trace Tells You What Happened. Langfuse Metrics Tell You What It Costs.
- Your Langfuse Traces Are Already Yours. Here Is How You Get Them Out.
- Your Langfuse Traces Are Customer Data. Mask Them Before They Leave.