Replies: 3 comments
-
Same problem here tbh. Upvoted. |
Beta Was this translation helpful? Give feedback.
-
Thanks for raising this. The Related: #1716 Proposed change: #1717 |
Beta Was this translation helpful? Give feedback.
-
Released in https://github.com/langfuse/langfuse/releases/tag/v2.36.0 |
Beta Was this translation helpful? Give feedback.
-
Hey! First of all, thanks for the great tool. We have a product with millions AI requests monthly and with Langfuse we were able to analyze costs and user behavior. So the tool is a livesaver.
Unfortunately, since we have thousands of users making hundreds AI actions each, we see that our self-hosted Langfuse database gets 3 GB bigger every day.
We are planning to implement some automatic cleanup of
input
andoutput
fields for old records intraces
andobservations
tables (is it safe?). It is a thing we probably can do ourselves, but I decided to let you know that there is a demand for this kind of feature since everyone probably needs historical data about costs and trace count only (no need to read X-month-old prompts and output bodies).We have also noticed that over 60% of the database size is
events
table which we probably don't need at all, so my questions are:Thanks!
Beta Was this translation helpful? Give feedback.
All reactions