Postgres table audit_logs filling up in langfuse open source

[TheJKM]

I'm using the open source version of langfuse (currently v3.130.0), and I'm seeing the audit_logs table in postgres growing to more than 6GB.
As those audit logs are not usable in the OSS edition, why is this data being collected at all?
How can I get rid of it? Is it safe to simply execute a DELETE FROM audit_logs?

[inkeep-ai-assistant[bot]]

Audit logs are an enterprise feature in Langfuse and are not accessible or usable in the open source (OSS) edition(1)(2)(3). However, audit log entries are still collected in the database, which can cause the audit_logs table in Postgres to grow over time(1)(2)(3).

There is no official documentation specifying a built-in way to purge or disable audit log collection in the OSS edition. Deleting entries from the audit_logs table (e.g., running DELETE FROM audit_logs) is not documented as unsafe, but there is also no explicit guarantee in the sources that this operation is officially supported. Proceeding with such direct database operations is at your own risk, and it is recommended to back up your database before making changes(4)(2).

📚 Sources:

1. Audit Logs
2. Why is Langfuse Open Source? - Langfuse Handbook
3. Open Sourcing All Product Features
4. Postgres Database

---

Have another question? Just tag @inkeep.

[Steffen911]

@TheJKM In case you'd ever want to upgrade, you can see the audit_log history of your service within the UI. That's why we collect them, even on open source, self-hosted instances.

They're not being used or referenced anywhere else, so if you truncate the table this shouldn't cause any issues within your application.

[TheJKM]

Thank you for your reply! I have already deleted the entries, otherwise storage would have been filled 100% by now.

I'd then suggest to make this configurable via environment variable for an upcoming version.

[keyoumao]

This is a great post, we are kinda of the opposite: @Steffen911 If we want to use the audit logs stored in Postgres, do we need to pay the enterprise version?
cc: @sspatharioti @tpanza

[Steffen911]

@keyoumao The enterprise version enables audit log access within the UI. If you read them directly from Postgres, this shouldn't violate the license as the underlying data is yours.

[keyoumao]

Thank you @Steffen911 ! we can definitely look into the direct audit log first.