I am migrating the log4j library from 1.2.17 to 2.14.1 and facing issues
with the custom appenders.
I have tried all the other solutions for the problem that I could find with
regards to syntax, classloader, using the 'packages' attribute. But I am
still unable to initialize the custom appender.
P
Firing events at a certain rate. The test configures the rolling file
appender to roll over once a second.
Specifically, the test ensures that the following works:
* Write log line 1 <-- second 1
* Write log line 2 <-- second 1
* Write log line 3, causes rollover <-- second 2
* Write log line 4 <
As a committer, yes, feel free to use the dev field. The due-to field
is used for contributions from outside the project.
On Thu, Jul 1, 2021 at 4:48 PM Raman Gupta wrote:
>
> FYI:
>
> https://issues.apache.org/jira/browse/LOG4J2-3116
>
> https://github.com/apache/logging-log4j2/pull/543
>
> One
FYI:
https://issues.apache.org/jira/browse/LOG4J2-3116
https://github.com/apache/logging-log4j2/pull/543
One administrative note -- as I am a committer (although thus far I have
only committed to the log4j2 kotlin repo) should I do dev="rgupta" instead
of adding myself in due-to?
Some technical
What do you exactly mean by "ensuring"? Checking if the event rate was
correct? Or rather firing events at a certain rate? For the former, you can
collect all the events, split the collection into buckets of seconds, and
count the number of events in each bucket. For the latter, did you try busy
sp
That is a great idea Raman! Would you mind creating a PR along with a Jira
ticket, please? I would appreciate if you can take the following into
account:
- Target release-2.x branch for the PR
- Prefix the PR title with the Jira ticket id
- Update json-template-layout.adoc.vm (See the "pr
Hi all,
as far as I know, PMCs have the carma to create repos.
And sure ... happy to do a rough plan before starting to write code. As
long as it's not like writing a RFC document. If you or someone here
could setup a root document, we could start writing and drawing.
Chris
On 01.07.21 17:23
Looks like a nifty feature!
On Wed, Jun 30, 2021 at 5:09 PM Raman Gupta wrote:
>
> I was thinking about contributing a JsonTemplateLayout for the structured
> logging format expected by Google Cloud Logging [1].
>
> This is what I've come up with so far: any comments are welcome:
> https://gist
Yes, I understand what you are asking for. From what I can see that would
involve
creating our Log4Go (wish we could use that name) to emulate Log4j as much as
possible and then creating separate Appender projects to pass events to logrus,
zerolog, etc. Typically, I would expect those framework
Davyd,
You have commit rights but I am not sure if that gives you the ability to
create a new repo. But before doing that I would create a confluence page to
lay out the initial requirements and design.
If you can’t create a repo and would like one I can certainly help with that.
Ralph
> On J
Hi Ralph and others,
right now the thing that annoys me most is that for example in PLC4Go we
used zerolog ... in an application at work we used logrus. Now I needed
to setup a configuration to sync the config of zerolog with that of
logrus. This is just annoying. With my proposed log4go API, I
11 matches
Mail list logo
