We have try to use lager as our log framework. But we meet some problem.
lager may lost some date, we have saw the source code of lager, I think the reason is that gen_event notify is a async call, It doesn't guarantee to message receiving.
lager performance is not good enough. I just guess it is because of lager's file backend is written by erlang. So it doesn't have a good performance.
So, I think a log framework written by C, and capsulated by Erlang may be a good choice.
Do you know any Erlang framework meet the requirements?
lager create a event named 'lager_event' in the application.
For every backend, there is only one gen_event process to handle it. Therefore if too many process generating messages at the same time, log will of course be lost at one specific time. It is not related to which language do you use.
Sugguest: 1. control log quantity. 2. get rid of the erlang's event system and create a jobs(tasks)'s subsystem (multi processes) to handle log.