Long-Term Analysis of Langfuse LLM Traces with ClickHouse
A verification log on normalizing Langfuse Observations and Scores into ClickHouse, then using SQL to inspect model-level cost, prompt-version quality trends, and retry-driven cost increases.
Tag
#langfuse
The Loop Ran, but I Could Not Tell What Worked
A verification article on sending a generate, evaluate, feedback, and regenerate loop to Langfuse so the improvement path can be traced by attempt, not just by final output.
Saving Eve Eval Failures to Langfuse Datasets to Improve Evaluation Criteria
A validation note on sending a failed Eve weather-tool eval to Langfuse, comparing the failed run with a revised run, and improving the evaluation criteria.
Can Langfuse Assistant Serve as an Entry Point for Operations Investigation?
Testing the Langfuse Assistant public beta against existing Sakana Fugu observations and ground truth calculated through the Public API.
Observing the Sakana Fugu API with Langfuse: Understanding Hidden Costs in Multi-Agent Systems
A hands-on report instrumenting Sakana Fugu's OpenAI-compatible API with Langfuse, measuring how latency, token consumption, and TTFT change across Level 1–3 tasks.
Observing the Black Box of a Multi-Agent API with Sakana Fugu and Langfuse
I subscribed to Sakana Fugu to understand its nature as an OpenAI-compatible API and to plan how to observe its black-box cooperative reasoning from the outside.
Streaming Flue Observe Events to Langfuse: Monitoring an Issue Triage Agent
An experiment log where I redact Flue 1.0 Beta observe events before sending them to Langfuse, tracking the issue triage workflow's runId, model, and results.
Observing Eve TUI Execution and Tool Calls with Langfuse
A hands-on comparison of two ways to send Eve tool-calling executions to Langfuse as trace/span/generation data.
Building a Langfuse Morning Briefing for Slack
A practical experiment that aggregates Langfuse traces in a Cloudflare Worker and sends only token, cost, and latency anomalies to Slack.
I Want to Build a Langfuse Morning Briefing That Pushes Only Anomalies to Slack
Manually checking traces every day is unsustainable. A personal GenAIOps plan to aggregate Langfuse failures, token spikes, and low-score outputs into a single Slack morning briefing.