[
https://issues.apache.org/jira/browse/KARAF-4546?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15316673#comment-15316673
]
ASF subversion and git services commented on KARAF-4546:
--------------------------------------------------------
Commit 145e396199d1eba93a5a2ac119993516cbdb488e in karaf-decanter's branch
refs/heads/master from [[email protected]]
[ https://git-wip-us.apache.org/repos/asf?p=karaf-decanter.git;h=145e396 ]
[KARAF-4546] Fix test fail
> Support embedding decanter into spring boot apps
> ------------------------------------------------
>
> Key: KARAF-4546
> URL: https://issues.apache.org/jira/browse/KARAF-4546
> Project: Karaf
> Issue Type: New Feature
> Components: decanter
> Affects Versions: decanter-1.1.0
> Reporter: Christian Schneider
> Assignee: Christian Schneider
> Fix For: decanter-1.1.1
>
>
> I just did a POC to use decanter as a distributed logging system for spring
> boot applications.
> My first approach was to use the log4j socket appender to log into a local
> (but separate process) decanter-agent that then forwards to kafka.
> A central decanter server would then pick up the logs and store them into ES.
> The disadvantage was that each node needs a local decanter-agent which makes
> the packaging for the cloud more difficult.
> So I looked into a way to embed decanter into spring boot and found felix
> connect. It allows to pick some bundles from the normal classpath and start
> them in a partial OSGi container.
> It seems to be good enough to nicely host decanter and the kafka appender. I
> created a custom logback appender class for spring boot that forwards all
> logs into the embedded decanter instance.
> To make it easy to use I packaged this as a spring boot starter. So people
> only have to add the dependency and configure their logging to use the new
> decanter appender.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
