You do know that we are talking about the Flume documentation here, not Log4j?
I don’t know how we could do that with Jenkins as Jenkins would have to be
given commit rights.
Ralph
> On Feb 10, 2016, at 5:22 PM, Matt Sicker wrote:
>
> Can we set up a Jenkins job to auto-deploy the latest sit
We might need to make some modifications in the template. Otherwise you'll
get some fun references to the previous release.
On 10 February 2016 at 18:31, Gary Gregory wrote:
> We would also need to mod the release site to point to the snapshot site.
>
> Gary
> On Feb 10, 2016 4:22 PM, "Matt Sick
We would also need to mod the release site to point to the snapshot site.
Gary
On Feb 10, 2016 4:22 PM, "Matt Sicker" wrote:
> Can we set up a Jenkins job to auto-deploy the latest site and javadocs?
>
> On 10 February 2016 at 16:04, Ralph Goers
> wrote:
>
> > If is in the docs in git, not on t
Can we set up a Jenkins job to auto-deploy the latest site and javadocs?
On 10 February 2016 at 16:04, Ralph Goers
wrote:
> If is in the docs in git, not on the web site yet.
>
> Ralph
>
> > On Feb 10, 2016, at 2:52 PM, Gary Gregory
> wrote:
> >
> > Hi,
> >
> > Do you have docs on how to use th
If is in the docs in git, not on the web site yet.
Ralph
> On Feb 10, 2016, at 2:52 PM, Gary Gregory wrote:
>
> Hi,
>
> Do you have docs on how to use the feature? Is it in Javadoc does one neex
> to build the site locally to read all about it?
>
> I wonder if we should have a snapshot site u
I was actually thinking that we might create a lookup that parses the results
from other lookups. I’m just not sure what the syntax would be.
Ralph
> On Feb 10, 2016, at 2:49 PM, Gary Gregory wrote:
>
> It sounds like a pretty generic feature though. And making life easier for
> log4j1 migrat
Hi,
Do you have docs on how to use the feature? Is it in Javadoc does one neex
to build the site locally to read all about it?
I wonder if we should have a snapshot site up for this kind of unreleased
feature?
Gary
On Feb 10, 2016 1:09 PM, "Ralph Goers" wrote:
> As it happens I just committed
It sounds like a pretty generic feature though. And making life easier for
log4j1 migratory users is a huge bonus IMO.
How about contributing this as a patch?
Gary
On Feb 10, 2016 1:32 PM, "Ralph Goers" wrote:
> Yes, they are discrete attributes in Log4j2. However, you should be able
> to handl
Yes, they are discrete attributes in Log4j2. However, you should be able to
handle this using your own Lookup. For example you could do:
Then implement ZooLookup to parse the zookeeper.root.logger environment
variable and return the values for rootLevel and rootAppender.
Ralph
> On Feb
Hello Log4J community,
I'm currently investigating possible migration from Log4J 1 to Log4J 2 for
Apache ZooKeeper. For full context, please see Apache JIRA issue
ZOOKEEPER-2342 [1]. I'm struggling with how to preserve one particular
capability that we have already given to administrators for co
As it happens I just committed an enhancement to Flume that allows you to add a
prefix and file extension to the file. The default PathManager creates the file
name at start up and uses the start time as the string you are seeing. I
created a RollTimePathManager that creates a new timestamp in a
I got a Flume appender with Remote working. I have flume agent configured
to write to a file. That's working. However, the file is named something
randomish,1455134507011-1. Is there anyway to specify the filename to
write to?
On Wed, Feb 10, 2016 at 10:54 AM, Tara Czutno
wrote:
> I finally
I finally Flume in Remote mode working.
pom.xml add:
org.apache.logging.log4j
log4j-flume-ng
${log4j2Version}
config:
On Tue, Feb 9, 2016
Vanilla would work for my case.
On Tue, Feb 9, 2016 at 8:49 PM, Ralph Goers
wrote:
> The 3 types are:
>
> Vanilla - it uses Flume’s RPC client to send events to a remote Flume
> instance synchronously. If the remote Flume goes down you could lose
> events. It requires a minimum of dependencies.
14 matches
Mail list logo
