separate logfile per vhost/database about lager HOT 8 CLOSED

I'm planning to do something like this, but more powerful. I just haven't had the time to get around to implementing it.

Instead of logging to a particular file, you'll specify some 'attributes' for the log message, eg. vhost, vnode, requestID, etc and then you'll set up filters on the output files so that you can create logfiles that log for a particular vhost, if you wish.

from lager.

sounds great.

from lager.

Any ideas when we will see this very cool feature?

from lager.

There's an initial implementation over in https://github.com/basho/lager/tree/adt-atomic-tracer . It has a few remaining rough edges and I need to write some documentation, but hopefully it'll be up for review in the next week or so.

from lager.

Thank you very much! I am really looking for a logging solution. At the moment I use SASL and elogger https://github.com/etnt/elogger. I use elogger mostly because of its performance. It is fast because because it is based on disk_log

So, I want to know if you did any load tests over Lager?

from lager.

Alright, the tracing stuff has been merged into master now. Let me know if it works/doesn't work for you.

I do have a lager benchmark blog post cooking on the back burner, although I didn't test elogger, I might add it to the list.

from lager.

Looking forward for your blog post! Could you provide me a link, so I subscribe for it please?

from lager.

andrew.hijacked.us, although I think it'll end up reposted on the basho blog as well.

from lager.