The easiest way to do this regardless of which logging backend you're using in Karaf is to implement this pax-logging service: < https://github.com/ops4j/org.ops4j.pax.logging/blob/master/pax-logging-api/src/main/java/org/ops4j/pax/logging/spi/PaxAppender.java >.
If you're using pax-logging-log4j2 (I don't remember if it's the default yet in 4.0.x), then the docs on writing appenders is here: http://logging.apache.org/log4j/2.x/manual/extending.html On 18 November 2016 at 03:05, Niten Aggarwal <[email protected]> wrote: > Hi All, > > Has anyone integrated custom log appender with Karaf 4.0.7? > It would be great if you can share link and usage? > > > Thanks > Nitin > > > > ::DISCLAIMER:: > ------------------------------------------------------------ > ------------------------------------------------------------ > ---------------------------- > > The contents of this e-mail and any attachment(s) are confidential and > intended for the named recipient(s) only. > E-mail transmission is not guaranteed to be secure or error-free as > information could be intercepted, corrupted, > lost, destroyed, arrive late or incomplete, or may contain viruses in > transmission. The e mail and its contents > (with or without referred errors) shall therefore not attach any liability > on the originator or HCL or its affiliates. > Views or opinions, if any, presented in this email are solely those of the > author and may not necessarily reflect the > views or opinions of HCL or its affiliates. Any form of reproduction, > dissemination, copying, disclosure, modification, > distribution and / or publication of this message without the prior > written consent of authorized representative of > HCL is strictly prohibited. If you have received this email in error > please delete it and notify the sender immediately. > Before opening any email and/or attachments, please check them for viruses > and other defects. > > ------------------------------------------------------------ > ------------------------------------------------------------ > ---------------------------- > > -- Matt Sicker <[email protected]>
