Self-hosted Langfuse: tracing 7% of my AI agents, and ClickHouse logging itself

说明与用途

作者自托管 Langfuse 监控 AI 代理，但最初仅在一个配置文件中启用跟踪，导致仅 7% 的覆盖率并导致 ClickHouse 磁盘使用过多。通过为所有配置文件设置密钥、环境标签并禁用系统日志，覆盖率提升至 100%，磁盘空间减少近一半。

问题

Only 7% of AI agent traffic was traced and ClickHouse consumed 6 GiB of disk for 2.2 MiB of trace data, obscuring performance insights and wasting resources.

结果

Tracing coverage increased from 7 % to 100 % across profiles, enabling accurate latency and cost analysis per role. ClickHouse disk usage dropped by ~50 % after disabling unnecessary system logs, improving I/O performance.

工作流

• 1. Copy Langfuse API keys into each profile’s secret scope. 2. Enable the Langfuse tracing plugin for each profile. 3. Set the Langfuse environment to the profile name. 4. Restart the gateway and send a probe trace from each profile to verify tagging. 5. Create a ClickHouse config.d file that removes twelve system log tables and sets logger level to warning. 6. Mount the config file read‑only into the container and recreate it. 7. Verify container health, unchanged trace_log row count, and intact trace data.
• 8. Run a weekly script that compares session records with Langfuse traces to generate role‑based reports.

证据

Langfuse held 618 events across 79 traces in four weeks. That's about three traces a day.

来源

ClickHouse was using 6.03 GiB of disk. The actual Langfuse trace data in it was 2.2 MiB.

来源

The tracing plugin is enabled per profile, and it reads its Langfuse API keys through that profile's own secret scope.

来源

ClickHouse lets you override server config with a file dropped into /etc/clickhouse-server/config.d/. This one removes twelve system log tables...

来源