You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Today, Lilith keep large volumes of customer data that are related to the events received post:
/.lilith/logs/*. lilith
This can quickly represent several gigabytes of data on disk.
Should be able to afford to keep this history while compressing the data (zip) on the client.
A purge of compressed sliding window data would be interesting (max 3 last month)
The text was updated successfully, but these errors were encountered:
Each event is actually already separately gzipped binary so they won't compress that well. A single event takes an average of about 800 bytes in case of our production systems. This is mainly because of the full callstacks, throwable stacktraces and MDC data that are still included - something that you wouldn't have in case of the usual text logs.
Not sure if you are aware of this:
You can disable the global log (the file that contains every single event received, regardless of source) in the general preferences. This would effectively half the size Lilith uses up.
There is also an option to automatically delete all logs while closing Lilith. The setting is hidden in "Startup & Shutdown".
There's a "Clean all inactive logs." action in the file menu. This won't delete the global log, though.
Hope this helps...
Don't get me wrong but it makes me quite happy that you are using Lilith in such an extensive way. :)
Today, Lilith keep large volumes of customer data that are related to the events received post:
/.lilith/logs/*. lilith
This can quickly represent several gigabytes of data on disk.
Should be able to afford to keep this history while compressing the data (zip) on the client.
A purge of compressed sliding window data would be interesting (max 3 last month)
The text was updated successfully, but these errors were encountered: