You are viewing a plain text version of this content. The canonical link for it is here.
Posted to user@karaf.apache.org by Владимир Коньков <vk...@citc.ru> on 2016/03/16 11:32:31 UTC
Consider adding GELF Log4J 2 appender in Karaf 4.1.x by default
Hi
As of version 4.1 Karaf will use Log4J 2 as logging backend (thanx, Guillaume). It’s very good news, because it greatly simplify configuration of robust production logging - compression, flexible rotation rules, async, fallback logging. All this features comes out of the box with Log4J 2. No more custom appenders needs to be installed at first start time to achieve basic production quality configuration.
But for advanced production logging one option is missing out of the box - logging analysis tools integration, line ELK, Fluentd, Graylog, Splunk. To achieve this capability in robust way we should again install custom appender ( like https://github.com/Graylog2/log4j2-gelf <https://github.com/Graylog2/log4j2-gelf> ) at first start time.
I know, it can be installed as regular bundle fragment after first startup. But installing appender this way has some drawbacks that make it unacceptable for production usage:
1. First startup logs not coming in appender installed after start. (stopper for automated deployments)
2. If appender configured before bundle cache initialization - there is errors in file logs about missing appender class. Cache clean up is not so rare on production deployment, usually it is simpler to clean cache before some major software update that dealing with deps conflicts on upgrade.
3. After installation of custom appender bundle host bundle should be refreshed (some log entries may be lost).
If custom appender is MAIN logging channel restriction above not acceptable for us. Workaround is simple but very inconvenient to support for different versions of Karaf:
- add appender jar to system lib
- modify startup.properties to incude appender bundle
My proposal: include GELF Log4J 2 appender in standart distribution. In such way we provide log streaming capability to all major logging analysis tools. Because of growing adoption of log analysis tools it may be good addition to Karaf feature portfolio in addition to own solution Decanter.
I can provide PR on Github with carefully repackaged appender lib that not export anything to other bundles.
What do you think?
Thanx,
Vladimir Konkov
Re: Consider adding GELF Log4J 2 appender in Karaf 4.1.x by default
Posted by Владимир Коньков <vk...@citc.ru>.
Hi JB,
After adoption one of log4j2 GELF appenders I’ve share results with example configuration. Installation process of custom appender in general already properly documented in section «Custom appenders» of User Guide.
Configuration example for gelfj appender for current Karaf (log4j 1.x) releases:
1. Install bundle in any way:
mvn:org.graylog2/gelfj/1.1.14
2. Modify config file org.ops4j.pax.logging.cfg by adding section:
# Async wrapper for send queue in case of GELF destination is unavailable
log4j.appender.gelfasync=org.apache.log4j.AsyncAppender
log4j.appender.gelfasync.blocking=false
log4j.appender.gelfasync.bufferSize=20000
log4j.appender.gelfasync.appenders=gelf
# Define the GELF destination
log4j.appender.gelf=org.graylog2.log.GelfAppender
log4j.appender.gelf.graylogHost=tcp:<gelf_receiver_host>
log4j.appender.gelf.graylogPort=<gelf_receiver_port>
log4j.appender.gelf.facility=karaf
log4j.appender.gelf.layout=org.apache.log4j.PatternLayout
log4j.appender.gelf.extractStacktrace=true
log4j.appender.gelf.addExtendedInformation=true
log4j.appender.gelf.includeLocation=false
log4j.appender.gelf.additionalFields={'environment': 'QA'}
3. Modify config file org.ops4j.pax.logging.cfg by adding appender ‘gelfasync’ to global appenders list. Example:
log4j.rootLogger=INFO, out, osgi:*, gelfasync
Regards,
Vladimir Konkov
CIT Consulting LLC
> 20 марта 2016 г., в 10:56, Jean-Baptiste Onofré <jb...@nanthrax.net> написал(а):
>
> Hi Valdimir,
>
> by feature, I meant "a simple way" to provide/add it (not necessary a Karaf feature) ;)
>
> Probably the easier way now is to document how to do it in the dev guide with an associated sample.
>
> Regards
> JB
>
> On 03/19/2016 03:03 PM, Владимир Коньков wrote:
>> Hi Jean-Baptiste!
>>
>> We actively use GELF for streaming logs from Karaf based platforms for
>> years. But we stop building custom distributions at beginning of
>> adoption because of we use use different distrs from different vendors
>> (FuseSource, Talend, stock Servicemix, plain Karaf etc). Not all distrs
>> can be modified. It all needs to be upgradable.
>> Custom distribution is not practical way for us. Now we install appender
>> at deployment time by help of deployment automation tools like Ansible,
>> Puppet.
>>
>> Current appender we use is GELFJ. Not so robust as I want but with some
>> infrastructure support it works:
>>
>> https://github.com/t0xa/gelfj
>>
>> It is already has OSGI headers to be fragment bundle for Pax-Logging.
>>
>> For log4j2 I currently testing this 2 implementations:
>>
>> 1. https://github.com/Graylog2/log4j2-gelf
>>
>> 2. https://github.com/mp911de/logstash-gelf
>>
>> For fist I’ve made couple of changes + OSGI headers for both. If someone
>> is interested in I can share results after decision to be made with
>> small configuration example. As before, we not plan build custom distrs.
>>
>> I think Karaf feature is not to be needed because there is only one
>> proper way to package appender - one superbundle, fragment for
>> Pax-Logging without any exports and imports. Because of that -
>> installation of appender it is simple bundle installation and Karaf
>> restart. Or startup.properties modification, etc…
>>
>> Regards,
>> Vladimir Konkov
>> CIT Consulting LLC
>>
>>> 17 марта 2016 г., в 22:17, Jean-Baptiste Onofré <jb@nanthrax.net
>>> <mailto:jb@nanthrax.net <ma...@nanthrax.net>>> написал(а):
>>>
>>> Hi Vladimir
>>>
>>> anyway, do you already have GELF in your custom distribution ?
>>> If so, I would love to document it for other potential users, or even
>>> propose an optional feature to add this.
>>>
>>> WDYT ?
>>>
>>> Regards
>>> JB
>>>
>>> On 03/17/2016 06:33 AM, Владимир Коньков wrote:
>>>> Hi there!
>>>>
>>>> Lukasz, Jean-Baptiste, thanx for reply. Actually your opinion is
>>>> expected and reasonable.
>>>>
>>>> Lukasz, couple of comments:
>>>>
>>>> Proposed solution is not specific for any tool - GELF is very common
>>>> format for app log streaming and it’s popularity is growing.
>>>>
>>>> About custom distribution:
>>>> Usually, ops team is orthogonal to dev team. Infrastructure services
>>>> like logging provided by ops team, deployment platform stated by dev
>>>> team. It’s not comfortable to require custom version of Karaf from
>>>> dev team. Moreover it is not always possible. In our projects we
>>>> support many Karaf versions and distribution from Apache Servicemix
>>>> 4.4 (Karaf 2.2.x) to TalendESB 5.x to modern Karaf 4.0.x - it is far
>>>> from always possible to build custom distr. But on all of this distrs
>>>> we use one set of custom appenders (!) for 4+ years. One of that
>>>> appenders finally die (compression, file rotation etc), but not other.
>>>>
>>>> Lukasz is absolutely right - logging is part of foundation
>>>> functionalities and because of that it is hard to extend in
>>>> comparison to other parts. I’ve first voted for removing blueprint
>>>> from base distribution but ask you for common streaming log appender.
>>>>
>>>> Anyway, thanx for Karaf - it is very good platform for any server
>>>> solutions on JVM. Of cause if you want and can adapt it.
>>>>
>>>> Regards,
>>>> Vladimir Konkov
>>>>
>>>
>>> --
>>> Jean-Baptiste Onofré
>>> jbonofre@apache.org <ma...@apache.org> <mailto:jbonofre@apache.org <ma...@apache.org>>
>>> http://blog.nanthrax.net <http://blog.nanthrax.net/>
>>> Talend - http://www.talend.com <http://www.talend.com/>
>>
>
> --
> Jean-Baptiste Onofré
> jbonofre@apache.org <ma...@apache.org>
> http://blog.nanthrax.net <http://blog.nanthrax.net/>
> Talend - http://www.talend.com <http://www.talend.com/>
Re: Consider adding GELF Log4J 2 appender in Karaf 4.1.x by default
Posted by Jean-Baptiste Onofré <jb...@nanthrax.net>.
Hi Valdimir,
by feature, I meant "a simple way" to provide/add it (not necessary a
Karaf feature) ;)
Probably the easier way now is to document how to do it in the dev guide
with an associated sample.
Regards
JB
On 03/19/2016 03:03 PM, Владимир Коньков wrote:
> Hi Jean-Baptiste!
>
> We actively use GELF for streaming logs from Karaf based platforms for
> years. But we stop building custom distributions at beginning of
> adoption because of we use use different distrs from different vendors
> (FuseSource, Talend, stock Servicemix, plain Karaf etc). Not all distrs
> can be modified. It all needs to be upgradable.
> Custom distribution is not practical way for us. Now we install appender
> at deployment time by help of deployment automation tools like Ansible,
> Puppet.
>
> Current appender we use is GELFJ. Not so robust as I want but with some
> infrastructure support it works:
>
> https://github.com/t0xa/gelfj
>
> It is already has OSGI headers to be fragment bundle for Pax-Logging.
>
> For log4j2 I currently testing this 2 implementations:
>
> 1. https://github.com/Graylog2/log4j2-gelf
>
> 2. https://github.com/mp911de/logstash-gelf
>
> For fist I’ve made couple of changes + OSGI headers for both. If someone
> is interested in I can share results after decision to be made with
> small configuration example. As before, we not plan build custom distrs.
>
> I think Karaf feature is not to be needed because there is only one
> proper way to package appender - one superbundle, fragment for
> Pax-Logging without any exports and imports. Because of that -
> installation of appender it is simple bundle installation and Karaf
> restart. Or startup.properties modification, etc…
>
> Regards,
> Vladimir Konkov
> CIT Consulting LLC
>
>> 17 марта 2016 г., в 22:17, Jean-Baptiste Onofré <jb@nanthrax.net
>> <ma...@nanthrax.net>> написал(а):
>>
>> Hi Vladimir
>>
>> anyway, do you already have GELF in your custom distribution ?
>> If so, I would love to document it for other potential users, or even
>> propose an optional feature to add this.
>>
>> WDYT ?
>>
>> Regards
>> JB
>>
>> On 03/17/2016 06:33 AM, Владимир Коньков wrote:
>>> Hi there!
>>>
>>> Lukasz, Jean-Baptiste, thanx for reply. Actually your opinion is
>>> expected and reasonable.
>>>
>>> Lukasz, couple of comments:
>>>
>>> Proposed solution is not specific for any tool - GELF is very common
>>> format for app log streaming and it’s popularity is growing.
>>>
>>> About custom distribution:
>>> Usually, ops team is orthogonal to dev team. Infrastructure services
>>> like logging provided by ops team, deployment platform stated by dev
>>> team. It’s not comfortable to require custom version of Karaf from
>>> dev team. Moreover it is not always possible. In our projects we
>>> support many Karaf versions and distribution from Apache Servicemix
>>> 4.4 (Karaf 2.2.x) to TalendESB 5.x to modern Karaf 4.0.x - it is far
>>> from always possible to build custom distr. But on all of this distrs
>>> we use one set of custom appenders (!) for 4+ years. One of that
>>> appenders finally die (compression, file rotation etc), but not other.
>>>
>>> Lukasz is absolutely right - logging is part of foundation
>>> functionalities and because of that it is hard to extend in
>>> comparison to other parts. I’ve first voted for removing blueprint
>>> from base distribution but ask you for common streaming log appender.
>>>
>>> Anyway, thanx for Karaf - it is very good platform for any server
>>> solutions on JVM. Of cause if you want and can adapt it.
>>>
>>> Regards,
>>> Vladimir Konkov
>>>
>>
>> --
>> Jean-Baptiste Onofré
>> jbonofre@apache.org <ma...@apache.org>
>> http://blog.nanthrax.net
>> Talend - http://www.talend.com
>
--
Jean-Baptiste Onofré
jbonofre@apache.org
http://blog.nanthrax.net
Talend - http://www.talend.com
Re: Consider adding GELF Log4J 2 appender in Karaf 4.1.x by default
Posted by Владимир Коньков <vk...@citc.ru>.
Hi Jean-Baptiste!
We actively use GELF for streaming logs from Karaf based platforms for years. But we stop building custom distributions at beginning of adoption because of we use use different distrs from different vendors (FuseSource, Talend, stock Servicemix, plain Karaf etc). Not all distrs can be modified. It all needs to be upgradable.
Custom distribution is not practical way for us. Now we install appender at deployment time by help of deployment automation tools like Ansible, Puppet.
Current appender we use is GELFJ. Not so robust as I want but with some infrastructure support it works:
https://github.com/t0xa/gelfj <https://github.com/t0xa/gelfj>
It is already has OSGI headers to be fragment bundle for Pax-Logging.
For log4j2 I currently testing this 2 implementations:
1. https://github.com/Graylog2/log4j2-gelf
2. https://github.com/mp911de/logstash-gelf <https://github.com/mp911de/logstash-gelf>
For fist I’ve made couple of changes + OSGI headers for both. If someone is interested in I can share results after decision to be made with small configuration example. As before, we not plan build custom distrs.
I think Karaf feature is not to be needed because there is only one proper way to package appender - one superbundle, fragment for Pax-Logging without any exports and imports. Because of that - installation of appender it is simple bundle installation and Karaf restart. Or startup.properties modification, etc…
Regards,
Vladimir Konkov
CIT Consulting LLC
> 17 марта 2016 г., в 22:17, Jean-Baptiste Onofré <jb...@nanthrax.net> написал(а):
>
> Hi Vladimir
>
> anyway, do you already have GELF in your custom distribution ?
> If so, I would love to document it for other potential users, or even propose an optional feature to add this.
>
> WDYT ?
>
> Regards
> JB
>
> On 03/17/2016 06:33 AM, Владимир Коньков wrote:
>> Hi there!
>>
>> Lukasz, Jean-Baptiste, thanx for reply. Actually your opinion is expected and reasonable.
>>
>> Lukasz, couple of comments:
>>
>> Proposed solution is not specific for any tool - GELF is very common format for app log streaming and it’s popularity is growing.
>>
>> About custom distribution:
>> Usually, ops team is orthogonal to dev team. Infrastructure services like logging provided by ops team, deployment platform stated by dev team. It’s not comfortable to require custom version of Karaf from dev team. Moreover it is not always possible. In our projects we support many Karaf versions and distribution from Apache Servicemix 4.4 (Karaf 2.2.x) to TalendESB 5.x to modern Karaf 4.0.x - it is far from always possible to build custom distr. But on all of this distrs we use one set of custom appenders (!) for 4+ years. One of that appenders finally die (compression, file rotation etc), but not other.
>>
>> Lukasz is absolutely right - logging is part of foundation functionalities and because of that it is hard to extend in comparison to other parts. I’ve first voted for removing blueprint from base distribution but ask you for common streaming log appender.
>>
>> Anyway, thanx for Karaf - it is very good platform for any server solutions on JVM. Of cause if you want and can adapt it.
>>
>> Regards,
>> Vladimir Konkov
>>
>
> --
> Jean-Baptiste Onofré
> jbonofre@apache.org
> http://blog.nanthrax.net
> Talend - http://www.talend.com
Re: Consider adding GELF Log4J 2 appender in Karaf 4.1.x by default
Posted by Jean-Baptiste Onofré <jb...@nanthrax.net>.
Hi Vladimir
anyway, do you already have GELF in your custom distribution ?
If so, I would love to document it for other potential users, or even
propose an optional feature to add this.
WDYT ?
Regards
JB
On 03/17/2016 06:33 AM, Владимир Коньков wrote:
> Hi there!
>
> Lukasz, Jean-Baptiste, thanx for reply. Actually your opinion is expected and reasonable.
>
> Lukasz, couple of comments:
>
> Proposed solution is not specific for any tool - GELF is very common format for app log streaming and it’s popularity is growing.
>
> About custom distribution:
> Usually, ops team is orthogonal to dev team. Infrastructure services like logging provided by ops team, deployment platform stated by dev team. It’s not comfortable to require custom version of Karaf from dev team. Moreover it is not always possible. In our projects we support many Karaf versions and distribution from Apache Servicemix 4.4 (Karaf 2.2.x) to TalendESB 5.x to modern Karaf 4.0.x - it is far from always possible to build custom distr. But on all of this distrs we use one set of custom appenders (!) for 4+ years. One of that appenders finally die (compression, file rotation etc), but not other.
>
> Lukasz is absolutely right - logging is part of foundation functionalities and because of that it is hard to extend in comparison to other parts. I’ve first voted for removing blueprint from base distribution but ask you for common streaming log appender.
>
> Anyway, thanx for Karaf - it is very good platform for any server solutions on JVM. Of cause if you want and can adapt it.
>
> Regards,
> Vladimir Konkov
>
--
Jean-Baptiste Onofré
jbonofre@apache.org
http://blog.nanthrax.net
Talend - http://www.talend.com
Re: Consider adding GELF Log4J 2 appender in Karaf 4.1.x by default
Posted by Владимир Коньков <vk...@citc.ru>.
Hi there!
Lukasz, Jean-Baptiste, thanx for reply. Actually your opinion is expected and reasonable.
Lukasz, couple of comments:
Proposed solution is not specific for any tool - GELF is very common format for app log streaming and it’s popularity is growing.
About custom distribution:
Usually, ops team is orthogonal to dev team. Infrastructure services like logging provided by ops team, deployment platform stated by dev team. It’s not comfortable to require custom version of Karaf from dev team. Moreover it is not always possible. In our projects we support many Karaf versions and distribution from Apache Servicemix 4.4 (Karaf 2.2.x) to TalendESB 5.x to modern Karaf 4.0.x - it is far from always possible to build custom distr. But on all of this distrs we use one set of custom appenders (!) for 4+ years. One of that appenders finally die (compression, file rotation etc), but not other.
Lukasz is absolutely right - logging is part of foundation functionalities and because of that it is hard to extend in comparison to other parts. I’ve first voted for removing blueprint from base distribution but ask you for common streaming log appender.
Anyway, thanx for Karaf - it is very good platform for any server solutions on JVM. Of cause if you want and can adapt it.
Regards,
Vladimir Konkov
Re: Consider adding GELF Log4J 2 appender in Karaf 4.1.x by default
Posted by Jean-Baptiste Onofré <jb...@nanthrax.net>.
Hi,
I agree with Lukasz: I have no problem to document and improve the way
to include such appender in custom distribution, but I don't think it's
a good idea to have it shipped by default.
I could also be a Decanter new collector/appender (as we already have a
log collector/appender).
Regards
JB
On 03/16/2016 05:38 PM, Łukasz Dywicki wrote:
> Hey Vladimir,
> While I see reasoning to have this feature, I must say it is not a core
> requirement to all users. If we would decide to have such appender we
> easily can run into situation that everyone will want to have it’s own
> appender and it’s dependencies installed/available by default in Karaf.
> Sadly (in my perception) we can’t agree for that. If you would like to
> push this forward please answer to this mail and send reply to
> dev@karaf.apache.org <ma...@karaf.apache.org> so we could continue
> there. We need to keep in mind, that logging is part of foundation
> functionalities offered in Karaf available in same shape under minimal
> distribution.
>
> What I can recommend you is custom (re)packaging of Karaf. This will
> avoid troubles with manual modifications in configuration files and can
> be fully automated with maven tooling we offer. All you need to do is
> proper feature definition which will cause generation of
> startup.properties. You can also override default configuration files
> (ie. org.ops4j.pax.logging.cfg). In this way you will be able to produce
> Karaf assembly right for you, your clients and colleagues.
>
> Kind regards,
> Lukasz
> —
> Apache Karaf Committer & PMC
> Twitter: ldywicki
> Blog: http://dywicki.pl
> Code-House - http://code-house.org
>
>
>> Wiadomość napisana przez Владимир Коньков <vkonkov@citc.ru
>> <ma...@citc.ru>> w dniu 16 mar 2016, o godz. 11:32:
>>
>> Hi
>>
>> As of version 4.1 Karaf will use Log4J 2 as logging backend (thanx,
>> Guillaume). It’s very good news, because it greatly simplify
>> configuration of robust production logging - compression, flexible
>> rotation rules, async, fallback logging. All this features comes out
>> of the box with Log4J 2. No more custom appenders needs to be
>> installed at first start time to achieve basic production quality
>> configuration.
>>
>> But for advanced production logging one option is missing out of the
>> box - logging analysis tools integration, line ELK, Fluentd, Graylog,
>> Splunk. To achieve this capability in robust way we should again
>> install custom appender ( like https://github.com/Graylog2/log4j2-gelf
>> ) at first start time.
>>
>> I know, it can be installed as regular bundle fragment after first
>> startup. But installing appender this way has some drawbacks that make
>> it unacceptable for production usage:
>> 1. First startup logs not coming in appender installed after start.
>> (stopper for automated deployments)
>> 2. If appender configured before bundle cache initialization - there
>> is errors in file logs about missing appender class. Cache clean up is
>> not so rare on production deployment, usually it is simpler to clean
>> cache before some major software update that dealing with deps
>> conflicts on upgrade.
>> 3. After installation of custom appender bundle host bundle should be
>> refreshed (some log entries may be lost).
>>
>> If custom appender is MAIN logging channel restriction above not
>> acceptable for us. Workaround is simple but very inconvenient to
>> support for different versions of Karaf:
>> - add appender jar to system lib
>> - modify startup.properties to incude appender bundle
>>
>> My proposal: include GELF Log4J 2 appender in standart distribution.
>> In such way we provide log streaming capability to all major logging
>> analysis tools. Because of growing adoption of log analysis tools it
>> may be good addition to Karaf feature portfolio in addition to own
>> solution Decanter.
>>
>> I can provide PR on Github with carefully repackaged appender lib that
>> not export anything to other bundles.
>>
>> What do you think?
>>
>> Thanx,
>> Vladimir Konkov
>>
>
--
Jean-Baptiste Onofré
jbonofre@apache.org
http://blog.nanthrax.net
Talend - http://www.talend.com
Re: Consider adding GELF Log4J 2 appender in Karaf 4.1.x by default
Posted by Łukasz Dywicki <lu...@code-house.org>.
Hey Vladimir,
While I see reasoning to have this feature, I must say it is not a core requirement to all users. If we would decide to have such appender we easily can run into situation that everyone will want to have it’s own appender and it’s dependencies installed/available by default in Karaf. Sadly (in my perception) we can’t agree for that. If you would like to push this forward please answer to this mail and send reply to dev@karaf.apache.org <ma...@karaf.apache.org> so we could continue there. We need to keep in mind, that logging is part of foundation functionalities offered in Karaf available in same shape under minimal distribution.
What I can recommend you is custom (re)packaging of Karaf. This will avoid troubles with manual modifications in configuration files and can be fully automated with maven tooling we offer. All you need to do is proper feature definition which will cause generation of startup.properties. You can also override default configuration files (ie. org.ops4j.pax.logging.cfg). In this way you will be able to produce Karaf assembly right for you, your clients and colleagues.
Kind regards,
Lukasz
—
Apache Karaf Committer & PMC
Twitter: ldywicki
Blog: http://dywicki.pl
Code-House - http://code-house.org
> Wiadomość napisana przez Владимир Коньков <vk...@citc.ru> w dniu 16 mar 2016, o godz. 11:32:
>
> Hi
>
> As of version 4.1 Karaf will use Log4J 2 as logging backend (thanx, Guillaume). It’s very good news, because it greatly simplify configuration of robust production logging - compression, flexible rotation rules, async, fallback logging. All this features comes out of the box with Log4J 2. No more custom appenders needs to be installed at first start time to achieve basic production quality configuration.
>
> But for advanced production logging one option is missing out of the box - logging analysis tools integration, line ELK, Fluentd, Graylog, Splunk. To achieve this capability in robust way we should again install custom appender ( like https://github.com/Graylog2/log4j2-gelf <https://github.com/Graylog2/log4j2-gelf> ) at first start time.
>
> I know, it can be installed as regular bundle fragment after first startup. But installing appender this way has some drawbacks that make it unacceptable for production usage:
> 1. First startup logs not coming in appender installed after start. (stopper for automated deployments)
> 2. If appender configured before bundle cache initialization - there is errors in file logs about missing appender class. Cache clean up is not so rare on production deployment, usually it is simpler to clean cache before some major software update that dealing with deps conflicts on upgrade.
> 3. After installation of custom appender bundle host bundle should be refreshed (some log entries may be lost).
>
> If custom appender is MAIN logging channel restriction above not acceptable for us. Workaround is simple but very inconvenient to support for different versions of Karaf:
> - add appender jar to system lib
> - modify startup.properties to incude appender bundle
>
> My proposal: include GELF Log4J 2 appender in standart distribution. In such way we provide log streaming capability to all major logging analysis tools. Because of growing adoption of log analysis tools it may be good addition to Karaf feature portfolio in addition to own solution Decanter.
>
> I can provide PR on Github with carefully repackaged appender lib that not export anything to other bundles.
>
> What do you think?
>
> Thanx,
> Vladimir Konkov
>