Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Lilith is greedy ! #8

Closed
indeez opened this issue Jul 11, 2013 · 1 comment
Closed

Lilith is greedy ! #8

indeez opened this issue Jul 11, 2013 · 1 comment

Comments

@indeez
Copy link

indeez commented Jul 11, 2013

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)

image

@huxi
Copy link
Owner

huxi commented Jul 11, 2013

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. :)

@huxi huxi closed this as completed Feb 7, 2014
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants