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
