Hi GrowthBook team, Our audit logs have become very large, and accessing them has become a challenge. When trying to open the audit log window for certain features, it can take several minutes to load, often ending with a "fetch failed" message and the GrowthBook server is killed with OOM error. This happened because a bug caused GB API update function to be called repeatedly, creating numerous audit log entries. Now that the bug is fixed, new logs are generated at a normal rate. However, for features with thousands of existing logs, it’s still difficult to access the most recent entries. Is there a way to improve loading times for these large audit logs, delete them or another solution to help access recent entries more efficiently? Thank you!

Hi Margarita - can you open a GitHub issue for this? It's something we can fix, I just don't want to lose track of the issue

Hi Graham, I opened an issue - https://github.com/growthbook/growthbook/issues/3223