Our self-hosted Langfuse stack stored 14GB on disk, only 1.6GB of it was actual observation data
Of the 14 gigabytes our self-hosted @Langfuse stack was storing on disk, only 1.6 gigabytes was actual observation data. The rest was the tool logging its own internal queries about itself.
Memory told the same story. The full stack needs about 7.6 GB of RAM to run, and ClickHouse, its own time-series database, eats 5.6 GB of that before storing a single event of ours.
We chose self-hosting to cut cost and keep control of the data. What we got instead was a monitoring tool that needs its own monitoring, sized for its own overhead rather than for the product it's watching.
If you're weighing Langfuse for self-hosting, check what share of its footprint is genuinely your data versus the tool watching itself work. Ours was about 12 percent
u/Educational_Kale_172 — 1 day ago