Hi Heiko, Now I could say hi 'cause I got my laptop back, my wife hijacked it few hours ago. Here is the situation I'm facing which in the end is nobody's fault, bunch of APIs using different logging facilities, at the moment here is the list of APIs that logs:
- Akka with actor, remote and cluster which I delegated to akka-log4j2 - EclipseLink which I wrote my own Log4j2SessionLogger. - Vert.x which I have implemented their provided LogDelegate libraries. - HikariCP which uses Slf4j which I bridged with Log4j2 synchronous library calls. So with that list you can imagine it is not worth having an occupied actor doing logging *-nor the main dispatcher-*, instead let me use what handles that concern properly which in this case is Log4j2 async appenders blah blah. It might block, it might saturate, is OK but at least I'm now sure my whole application is logging asynchronously and it is centralized to an area that I have more control and can mitigate, I even have an async log4j2.xml for the console for my development environment and another async rolling files for test and production environments. That said, I think it is now worth having such freedom of choice between log sync or async, don't you think? Best regards, Guido. On Sunday, December 20, 2015 at 3:22:50 PM UTC, Heiko Seeberger wrote: > > Got it. Unfortunately that’s not possible right now because of the design > of Akka’s logging facility which is made up from a frontend (the API you > actually use for logging, based on Akka’s Actor based event stream) and the > specific backend (e.g. akka-log4j). > > Maybe something to consider for Akka Typed? Roland? > > Heiko > > > -- > > *Heiko Seeberger* > Home: heikoseeberger.de > Twitter: @hseeberger <https://twitter.com/hseeberger> > Public key: keybase.io/hseeberger > > On 20 Dec 2015, at 13:17, Guido Medina <[email protected] <javascript:>> > wrote: > > Sorry for brevity writing from phone which I hate. > > In a nutshell I would like your plugin akka-log4j to offer an extra class > to log directly without an actor in between which is your current > implementation, same applies for akka-slf4j. > > That way Akka system has a registered logger and my actors will continue > obtaining the logger instance from Akka system. > > -- > > Read the docs: http://akka.io/docs/ > Check the FAQ: > http://doc.akka.io/docs/akka/current/additional/faq.html > Search the archives: https://groups.google.com/group/akka-user > > --- > You received this message because you are subscribed to the Google Groups > "Akka User List" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to [email protected] <javascript:>. > To post to this group, send email to [email protected] > <javascript:>. > Visit this group at https://groups.google.com/group/akka-user. > For more options, visit https://groups.google.com/d/optout. > > > -- >>>>>>>>>> Read the docs: http://akka.io/docs/ >>>>>>>>>> Check the FAQ: >>>>>>>>>> http://doc.akka.io/docs/akka/current/additional/faq.html >>>>>>>>>> Search the archives: https://groups.google.com/group/akka-user --- You received this message because you are subscribed to the Google Groups "Akka User List" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at https://groups.google.com/group/akka-user. For more options, visit https://groups.google.com/d/optout.
