Hi Matt,
On Fri, 1 Dec 2023 at 18:25, Matt Sicker wrote:
>
> However, that does raise an interesting point: we could link to third party
> plugins and such to help curate it.
That is part of the plan for MS9:
1. Each JAR containing Log4j plugins will have some documentation
resources (e.g. `ME
Right, I think I misread that. However, that’s what the curation idea is for :)
—
Matt Sicker
> On Dec 1, 2023, at 18:47, Gary Gregory wrote:
>
> Of course RE Volkan, my first sentence must have been poorly written. I
> meant to say that I know who Volkan is and that he is great, but, that's
> n
Of course RE Volkan, my first sentence must have been poorly written. I
meant to say that I know who Volkan is and that he is great, but, that's
not the point. I was trying to say that a peronal GitHub account, in
general, can't be compared to an official Apache account.
Gary
On Fri, Dec 1, 2023,
I may be biased, but I wouldn’t consider Volkan a random GitHub user! However,
that does raise an interesting point: we could link to third party plugins and
such to help curate it.
> On Dec 1, 2023, at 5:00 AM, Gary Gregory wrote:
>
> Hi all,
>
> (Don't take his the wrong way Volkan ;-)
> As
Hi all,
(Don't take his the wrong way Volkan ;-)
Assuming that I don't know who you are, why would I pick a random github
user's custom appender instead of an official Log4j appender? If your
appender is "battle-tested", why not move it to Log4j (or Redis?)
Gary
On Fri, Dec 1, 2023, 4:08 AM Vol
I appreciate your thoughts on this subject. We can eventually convert this
into a chapter in the Log4j manual. My goal is to be able to make a
statement as follows:
*When Log4j is configured with Y, Y, Z settings, it can provide guaranteed
delivery against certain types of log sinks such as A, B,
Volkan,
Notice that neither of the links you have provided use the term “guaranteed
delivery”. That is because that is not really what they are providing. In
addition, notice that Logstash says "Input plugins that do not use a
request-response protocol cannot be protected from data loss”, and
