Re: Information regarding log4j-audit-api 1.0.1

I will beginning the work to upgrade that this weekend. Ralph > On Oct 19, 2023, at 6:02 AM, Shiplu Kundu wrote: > > Hi Team, > > For my current project I was using* log4j-audit-api* to print the audit log > of my application . > But the latest version for this plugin 1

Re: Information regarding log4j-audit-api 1.0.1

Hi Shiplu, On Thu, 19 Oct 2023 at 15:09, Shiplu Kundu wrote: > For my current project I was using* log4j-audit-api* to print the audit log > of my application . > But the latest version for this plugin 1.0.1 and last release was on 2018 > June, and also it is showing around 75 vul

Information regarding log4j-audit-api 1.0.1

Hi Team, For my current project I was using* log4j-audit-api* to print the audit log of my application . But the latest version for this plugin 1.0.1 and last release was on 2018 June, and also it is showing around 75 vulnerabilities. I searched over the internet but didn't receive any l

Re: Status of log4j-audit

t > to run locally. It was suggested I switch the UI to JavaFX but I have > never had the chance. > > FWWI - Log4j-Audit is the entire reason I created Log4j2. It cannot > work with SLF4J/Logback. > > Ralph > > >> On Oct 10, 2023, at 1:48 PM, Matt Sicker wrote: &g

Re: Status of log4j-audit

- Log4j-Audit is the entire reason I created Log4j2. It cannot work with SLF4J/Logback. Ralph > On Oct 10, 2023, at 1:48 PM, Matt Sicker wrote: > > Log4j Audit has multiple components: > > * Audit API for extending log4j-api with some additional audit logging APIs > * Tool

Re: Status of log4j-audit

Log4j Audit has multiple components: * Audit API for extending log4j-api with some additional audit logging APIs * Tool for managing your audit event schemata and such (the web app thing) * Tool for generating structured log classes from the event schemata Thus, in typical use, you can (and

Re: Status of log4j-audit

I think it would be nice to do a release just to update dependencies. Gary On Tue, Oct 10, 2023, 2:33 PM Christian Grobmeier wrote: > Hello, > > We have been talking about log4j-audit (same thread as with log4j-server). > > I have checked today after seeing Piotr's mes

Status of log4j-audit

Hello, We have been talking about log4j-audit (same thread as with log4j-server). I have checked today after seeing Piotr's message, and even after reading the readme, I am still trying to figure out the purpose of this product. That aside, I am concerned the last change was four year

Re: Log4j Audit

Sure Ralph > On Oct 10, 2023, at 2:05 AM, Piotr P. Karwasz wrote: > > Hi all, > > Since Log4j Audit will not be archived, could someone update its > dependencies? Dependabot has lots of security alerts about it: > > https://github.com/apache/logging-log4j-a

Log4j Audit

Hi all, Since Log4j Audit will not be archived, could someone update its dependencies? Dependabot has lots of security alerts about it: https://github.com/apache/logging-log4j-audit/security/dependabot Piotr

Re: proposal/idea for enhancement to log4j audit

Yes. ⁣Bob Mroczka​ Original Message From: Ralph Goers Sent: Mon Nov 25 22:24:56 CST 2019 To: dev@logging.apache.org Subject: Re: proposal/idea for enhancement to log4j audit If I understand what you are asking for is you want to define an event attribute that has a constant

proposal/idea for enhancement to log4j audit

I would like to propose an enhancement to allow the catalog to be extended to include 'properties' for events. A property being an attribute with an assigned value that would get added to the event when it is either instantiated or at the time logEvent is called. The reason I'm looking to do

Re: proposal/idea for enhancement to log4j audit

If I understand what you are asking for is you want to define an event attribute that has a constant value? Ralph > On Nov 25, 2019, at 7:21 PM, Bob wrote: > > I would like to propose an enhancement to allow the catalog to be extended to > include 'properties' for events. > > A property bei

proposal/idea for enhancement to log4j audit

I would like to propose an enhancement to allow the catalog to be extended to include 'properties' for events. A property being an attribute with an assigned value that would get added to the event when it is either instantiated or at the time logEvent is called. The reason I'm looking to do

Re: [logging-log4j-audit] release plans for 1.0.2?

I can help finish the release with any PMC-specific aspects. We can certainly help explain any release steps. Making a new release guide for the audit component would be great, too. On Sun, 2 Jun 2019 at 12:56, Ralph Goers wrote: > > I should also add that there are a couple of steps that have to

Re: [logging-log4j-audit] release plans for 1.0.2?

I should also add that there are a couple of steps that have to be performed by a PMC member but those are after the release vote. If feel up to giving it a try that would be great! Ralph > On Jun 2, 2019, at 10:54 AM, Ralph Goers wrote: > > Yes, I more or less follow the same process. Since

Re: [logging-log4j-audit] release plans for 1.0.2?

Yes, I more or less follow the same process. Since it uses Java 8 it doesn’t need to add the TLS property though. Ralph > On Jun 2, 2019, at 9:46 AM, Matt Sicker wrote: > > This looks to be one of the few components that doesn't have a dedicated > release guide on the wiki yet. This likely fol

Re: [logging-log4j-audit] release plans for 1.0.2?

This looks to be one of the few components that doesn't have a dedicated release guide on the wiki yet. This likely follows the same steps as the Log4j 2 release guide, though: https://cwiki.apache.org/confluence/display/LOGGING/Log4j+2+Release+Process On Sun, Jun 2, 2019 at 06:04, Andrei Ivanov

[logging-log4j-audit] release plans for 1.0.2?

Hi, I would really like to see 1.0.2 released. Do you think there's anything else that should go in? Is there a release procedure documented somewhere so I can do that myself? Thank you, Andrei

Re: [logging-log4j-audit] branch LOG4J2-2579 updated (8fcfbb5 -> 998525c)

ay, some revisions that were in the old version of the > >> > > branch are not in the new version. This situation occurs > >> > > when a user --force pushes a change and generates a repository > >> > > containing something like this: > >>

Re: [logging-log4j-audit] branch LOG4J2-2579 updated (8fcfbb5 -> 998525c)

> > > containing something like this: >> > > >> > > * -- * -- B -- O -- O -- O (8fcfbb5) >> > > \ >> > > N -- N -- N refs/heads/LOG4J2-2579 (998525c) >> > > >> > > You should already have

Re: [logging-log4j-audit] branch LOG4J2-2579 updated (8fcfbb5 -> 998525c)

\ > > > N -- N -- N refs/heads/LOG4J2-2579 (998525c) > > > > > > You should already have received notification emails for all of the O > > > revisions, and so the following emails describe only the N revisions > > > from the common base

Re: [logging-log4j-audit] branch LOG4J2-2579 updated (8fcfbb5 -> 998525c)

gt; > > Any revisions marked "omit" are not gone; other references still > > refer to them. Any revisions marked "discard" are gone forever. > > > > No new revisions were added by this update. > > > > Summary of changes: > > .../logging/log4j/audit/LogEventFactory.java | 29 > ++ > > .../logging/log4j/audit/AuditLoggerTest.java | 7 -- > > 2 files changed, 24 insertions(+), 12 deletions(-) > > > > > -- > Matt Sicker >

Re: [logging-log4j-audit] branch LOG4J2-2579 updated (8fcfbb5 -> 998525c)

"discard" are gone forever. > > No new revisions were added by this update. > > Summary of changes: > .../logging/log4j/audit/LogEventFactory.java | 29 > ++ > .../logging/log4j/audit/AuditLoggerTest.java | 7 -- > 2 files changed, 24 insertions(+), 12 deletions(-) > -- Matt Sicker

Re: [ApacheCon] Last minute CFP about Log4j Audit

form: > > > > Title: Standardized Audit Logging with Log4j Audit > > Category: General > > Abstract: > > > > Keeping an audit trail of any system is a fundamental concern of > > systems building that is oftentimes skipped over or neglected, just > >

Re: [ApacheCon] Last minute CFP about Log4j Audit

Gee, that sounds pretty interesting to me! Ralph > On May 12, 2019, at 9:33 PM, Matt Sicker wrote: > > Not sure about a public URL, so here are the details copied from the form: > > Title: Standardized Audit Logging with Log4j Audit > Category: General > Abstract: >

Re: [ApacheCon] Last minute CFP about Log4j Audit

Not sure about a public URL, so here are the details copied from the form: Title: Standardized Audit Logging with Log4j Audit Category: General Abstract: Keeping an audit trail of any system is a fundamental concern of systems building that is oftentimes skipped over or neglected, just like any

Re: [ApacheCon] Last minute CFP about Log4j Audit

Is there some place to view the CFP? I hope I will be able to attend ApacheCon this year so perhaps I will be able to help out. Ralph > On May 12, 2019, at 8:46 PM, Matt Sicker wrote: > > I submitted a last minute CFP on our new sub project, somewhat similar to > what I did for Log4j 2.0 in 20

[ApacheCon] Last minute CFP about Log4j Audit

I submitted a last minute CFP on our new sub project, somewhat similar to what I did for Log4j 2.0 in 2014. Here’s hoping it gets accepted! -- Matt Sicker

Re: CI for Log4j Audit

I took a glance at the log. I suspect it is something wrong in the test but I won’t be able to look at it until the workday is done. Ralph > On May 7, 2019, at 9:52 AM, Ralph Goers wrote: > > The “restrict where this job can be run” setting is trial and error. We > occasionally have Jenkins j

Re: CI for Log4j Audit

It might be easier to use a pipeline than a free style project, but maybe that's just me. You should be able to use https://github.com/apache/logging-log4j2/blob/master/Jenkinsfile and simplify it a bit as I doubt we need to run the tests on so many JDKs. You can create a pipeline build to edit the

Re: CI for Log4j Audit

The “restrict where this job can be run” setting is trial and error. We occasionally have Jenkins jobs blow up because the slave wasn’t set up for something that causes our jobs to fail so we manually exclude them. We would have to look at the test failures. Having them work on our laptops and

Re: CI for Log4j Audit

Oh, and you might want to disable email notifications until you figure out the configuration first. ;) On Tue, 7 May 2019 at 11:48, Matt Sicker wrote: > > It might be easier to use a pipeline than a free style project, but > maybe that's just me. You should be able to use > https://github.com/apa

Re: CI for Log4j Audit

I've copied the "Log4j 2 2.x" job and adjusted it and now there is https://builds.apache.org/view/L/view/Logging/job/Log4j%20Audit/ :-) I hope the label for "Restrict where this project can be run" is ok. I've read through the pom.xml and I've enabled the "integration-tests" profile, with a plan t

Re: CI for Log4j Audit

Great! On Tue, 7 May 2019 at 10:50, Andrei Ivanov wrote: > > Seems to work now, thanks :-) > > On Tue, May 7, 2019 at 6:48 PM Matt Sicker wrote: > > > Alright, I just added him to the hudson-jobadmin group. Andrei, can > > you check again? Might need to log out, not sure. > > > > On Tue, 7 May 2

Re: CI for Log4j Audit

Seems to work now, thanks :-) On Tue, May 7, 2019 at 6:48 PM Matt Sicker wrote: > Alright, I just added him to the hudson-jobadmin group. Andrei, can > you check again? Might need to log out, not sure. > > On Tue, 7 May 2019 at 10:39, Ralph Goers > wrote: > > > > I just reviewed the Jenkins wik

Re: CI for Log4j Audit

Alright, I just added him to the hudson-jobadmin group. Andrei, can you check again? Might need to log out, not sure. On Tue, 7 May 2019 at 10:39, Ralph Goers wrote: > > I just reviewed the Jenkins wiki which says you have to be in the appropriate > LDAP group. Unfortunately, only the PMC chair

Re: CI for Log4j Audit

I just reviewed the Jenkins wiki which says you have to be in the appropriate LDAP group. Unfortunately, only the PMC chair has update authority in that tool so Matt will have to fix this for you. Ralph > On May 7, 2019, at 8:26 AM, Ralph Goers wrote: > > At the very top of the menu on the le

Re: CI for Log4j Audit

Yes, that's where I was looking at, I see directly the "People" link, instead of the "New Item". On Tue, May 7, 2019 at 6:26 PM Ralph Goers wrote: > At the very top of the menu on the left under the Jenkins logo you should > see a “New Item” link. If you don’t then you don’t have the correct > p

Re: CI for Log4j Audit

I was able to log in, but I don't think I have enough permissions, I can only see the jobs and run them, but not configure new items. On Tue, May 7, 2019 at 6:10 PM Matt Sicker wrote: > I’m somewhat familiar with it if you need help. That may sound like an > understatement, but alas, that’s the

Re: CI for Log4j Audit

At the very top of the menu on the left under the Jenkins logo you should see a “New Item” link. If you don’t then you don’t have the correct permissions. Ralph > On May 7, 2019, at 8:22 AM, Andrei Ivanov wrote: > > I was able to log in, but I don't think I have enough permissions, I can > onl

Re: CI for Log4j Audit

I’m somewhat familiar with it if you need help. That may sound like an understatement, but alas, that’s the difference between being a developer and user of a product sometimes. Miss the forest for the trees so to say. 😁 On Tue, May 7, 2019 at 09:57, Ralph Goers wrote: > Use your ASF credentials

Re: CI for Log4j Audit

Use your ASF credentials. If you aren’t aware of it, you can manage your credentials at id.apache.org . Ralph > On May 7, 2019, at 6:58 AM, Andrei Ivanov wrote: > > I don't have that much experience with it, but I can try :-) > > What about Jenkins credentials/permissio

Re: CI for Log4j Audit

I don't have that much experience with it, but I can try :-) What about Jenkins credentials/permissions? On Tue, May 7, 2019 at 3:14 PM Apache wrote: > If you are familiar with Jenkins you should just be able to create one. > > Ralph > > > On May 7, 2019, at 12:53 AM, Andrei Ivanov > wrote: >

Re: CI for Log4j Audit

If you are familiar with Jenkins you should just be able to create one. Ralph > On May 7, 2019, at 12:53 AM, Andrei Ivanov wrote: > > Hi, > I'm trying to see if there's a CI job defined for the Audit project. > > I'm looking at https://builds.apache.org/view/L/view/Logging/ and I don't > see o

CI for Log4j Audit

Hi, I'm trying to see if there's a CI job defined for the Audit project. I'm looking at https://builds.apache.org/view/L/view/Logging/ and I don't see one. If I am correct, how can one be defined? Regards, Andrei

Re: [apache/logging-log4j-audit] maven-compiler-plugin 3.8.0 (#13)

1:24, Ralph Goers >> wrote: >> >>> Matt, >>> >>> Did you create a Jira issue and add that to changes.xml? Just like Log4j >>> I’d like to track all the changes with Jira. >>> >>> Ralph >>> >>>> On Dec 14, 2018, at

Re: [apache/logging-log4j-audit] maven-compiler-plugin 3.8.0 (#13)

es.xml? Just like Log4j >> I’d like to track all the changes with Jira. >> >> Ralph >> >> > On Dec 14, 2018, at 10:01 AM, Matt Sicker >> wrote: >> > >> > Merged #13 <https://github.com/apache/logging-log4j-audit/pull/13> >> in

Re: [apache/logging-log4j-audit] maven-compiler-plugin 3.8.0 (#13)

Dec 14, 2018, at 10:01 AM, Matt Sicker > wrote: > > > > Merged #13 <https://github.com/apache/logging-log4j-audit/pull/13> into > master. > > > > — > > You are receiving this because you are subscribed to this thread. > > Reply to this email direc

Re: [apache/logging-log4j-audit] maven-compiler-plugin 3.8.0 (#13)

Matt, Did you create a Jira issue and add that to changes.xml? Just like Log4j I’d like to track all the changes with Jira. Ralph > On Dec 14, 2018, at 10:01 AM, Matt Sicker wrote: > > Merged #13 <https://github.com/apache/logging-log4j-audit/pull/13> into > master

Re: [ANNOUNCE] Apache Log4j-Audit 1.0.1 released

On Thu, 13 Dec 2018 at 18:55, Ralph Goers wrote: > > The Apache Log4j Audit team is pleased to announce the Log4j Audit 1.0.1 > release! > > Apache Log4j Audit is a framework for performing audit logging using a > predefined catalog of audit events. It provides a tool

[ANNOUNCE] Apache Log4j-Audit 1.0.1 released

The Apache Log4j Audit team is pleased to announce the Log4j Audit 1.0.1 release! Apache Log4j Audit is a framework for performing audit logging using a predefined catalog of audit events. It provides a tool to create and edit audit events. It also provides a REST service to perform the

[RESULT][VOTE] Release Log4j Audit 1.0.1 rc1

The vote has passed received binding +1 votes from Gary Gregory, Matt Sicker and Ralph Goers. It also received a +1 vote from David Olorundare. No other votes were cast. I will continue the release process later today. Ralph

Re: [VOTE] Release Log4j Audit 1.0.1 RC1

+1 Ralph > On Dec 2, 2018, at 8:42 PM, Ralph Goers wrote: > > This is a vote to release Log4j-Audit 1.0.1, the second release of the Log4j > Audit project. > > Please download, test, and cast your votes on the log4j developers list. > [] +1, release the artifacts &

Re: [VOTE] Release Log4j Audit 1.0.1 RC1

Running the following fails: git clone https://github.com/apache/logging-log4j-audit.git cd logging-log4j-audit git fetch --tags git checkout tags/log4-audit-1.0.1-rc1 error: pathspec 'tags/log4-audit-1.0.1-rc1' did not match any file(s) known to git On Mon, 10 Dec 2018 at 10:39, Ga

Re: [VOTE] Release Log4j Audit 1.0.1 RC1

following fails: >> >> git clone https://github.com/apache/logging-log4j-audit.git >> cd logging-log4j-audit >> git fetch --tags >> git checkout tags/log4-audit-1.0.1-rc1 >> >> error: pathspec 'tags/log4-audit-1.0.1-rc1' did not match any file(s)

Re: [VOTE] Release Log4j Audit 1.0.1 RC1

Oh I just noticed there's a typo in the tag checkout. You're missing a "j". On Mon, 10 Dec 2018 at 10:54, Matt Sicker wrote: > Running the following fails: > > git clone https://github.com/apache/logging-log4j-audit.git > cd logging-log4j-audit > git fetch --

Re: [VOTE] Release Log4j Audit 1.0.1 RC1

t; > > > Nope, still no tags: > > https://github.com/apache/logging-log4j-audit-sample/tags > > > > Did you go a push your tag? > > > > Gary > > > > On Sat, Dec 8, 2018 at 12:32 PM Ralph Goers > > wrote: > > > >> I edited the

Re: [VOTE] Release Log4j Audit 1.0.1 RC1

amework.beans.factory.annotation.Autowired,org.springframework.test.context.ActiveProfiles,org.junit.Test,org.springframework.context.annotation.Bean,org.springframework.context.annotation.ComponentScan C:\temp\rc\logging-log4j-audit\log4j-catalog\log4j-catalog-git\src\test\java\org\apache\logging\log4

Re: [VOTE] Release Log4j Audit 1.0.1 RC1

Why are you looking at logging-audit-sample? That is not what is being released. Ralph > On Dec 10, 2018, at 8:10 AM, Gary Gregory wrote: > > Hi Ralph, > > Nope, still no tags: > https://github.com/apache/logging-log4j-audit-sample/tags > > Did you go a push your ta

Re: [VOTE] Release Log4j Audit 1.0.1 RC1

Hi Ralph, Nope, still no tags: https://github.com/apache/logging-log4j-audit-sample/tags Did you go a push your tag? Gary On Sat, Dec 8, 2018 at 12:32 PM Ralph Goers wrote: > I edited the message below to get rid of the extra stuff my email client > must have added. > > Ralph &g

Re: [VOTE] Release Log4j Audit 1.0.1 RC1

Ralph Goers > wrote: > > > > Gary, > > > > I did both > > > > git clone -b log4j-audit-1.0.1-rc1 > https://github.com/apache/logging-log4j-audit.git temp > > And > > git clone https://github.com/apache/logging-log4j-audit.git temp > > cd temp

Re: [VOTE] Release Log4j Audit 1.0.1 RC1

I edited the message below to get rid of the extra stuff my email client must have added. Ralph > On Dec 8, 2018, at 12:16 PM, Ralph Goers wrote: > > Gary, > > I did both > > git clone -b log4j-audit-1.0.1-rc1 > https://github.com/apache/logging-log4j-audit.git

Re: [VOTE] Release Log4j Audit 1.0.1 RC1

Gary, I did both git clone -b log4j-audit-1.0.1-rc1 https://github.com/apache/logging-log4j-audit.git <https://github.com/apache/logging-log4j-audit.git> temp And git clone https://github.com/apache/logging-log4j-audit.git <https://github.com/apache/logging-log4j-audit.git> temp

Re: [VOTE] Release Log4j Audit 1.0.1 RC1

Vote: +1 No problems encountered so far with this RC for my team’s project. Code for reference: https://github.com/jenkinsci/audit-log-plugin David

Re: [VOTE] Release Log4j Audit 1.0.1 RC1

eRefresh > > INFO: Refreshing > > org.springframework.context.support.GenericApplicationContext@3e6fa38a: > > startup date [Thu Dec 06 08:50:17 MST 2018]; root of context hierarchy > > Tests run: 11, Failures: 0, Errors: 1, Skipped: 0, Time elapsed: 5.939 > sec > > <

Re: [VOTE] Release Log4j Audit 1.0.1 RC1

pareRefresh > > INFO: Refreshing > > org.springframework.context.support.GenericApplicationContext@3e6fa38a: > > startup date [Thu Dec 06 08:50:17 MST 2018]; root of context hierarchy > > Tests run: 11, Failures: 0, Errors: 1, Skipped: 0, Time elapsed: 5.939 > sec > > <<< FAILURE! -

Re: [VOTE] Release Log4j Audit 1.0.1 RC1

pped: 0, Time elapsed: 5.939 > sec > > <<< FAILURE! - in org.apache.logging.log4j.catalog.git.CatalogTest > > testRetrieveCatalog(org.apache.logging.log4j.catalog.git.CatalogTest) > Time > > elapsed: 3.439 sec <<< ERROR! > > org.apache.loggi

Re: [VOTE] Release Log4j Audit 1.0.1 RC1

17 MST 2018]; root of context hierarchy > Tests run: 11, Failures: 0, Errors: 1, Skipped: 0, Time elapsed: 5.939 sec > <<< FAILURE! - in org.apache.logging.log4j.catalog.git.CatalogTest > testRetrieveCatalog(org.apache.logging.log4j.catalog.git.CatalogTest) Time > elapsed: 3.439 sec <

Re: [VOTE] Release Log4j Audit 1.0.1 RC1

.apache.logging.log4j.catalog.api.exception.CatalogNotFoundException: Unable to clone remote catalog at https://git-wip-us.apache.org/repos/asf/logging-log4j-audit-sample.git to C:\Users\ggregory\AppData\Local\Temp\/audit/catalog at org.apache.logging.log4j.catalo

Re: [VOTE] Release Log4j Audit 1.0.1 RC1

On Wed, Dec 5, 2018 at 2:18 PM Gary Gregory wrote: > On Sun, Dec 2, 2018 at 8:42 PM Ralph Goers > wrote: > >> This is a vote to release Log4j-Audit 1.0.1, the second release of the >> Log4j Audit project. >> >> Please download, test, and cast your votes on th

Re: [VOTE] Release Log4j Audit 1.0.1 RC1

On Sun, Dec 2, 2018 at 8:42 PM Ralph Goers wrote: > This is a vote to release Log4j-Audit 1.0.1, the second release of the > Log4j Audit project. > > Please download, test, and cast your votes on the log4j developers list. > [] +1, release the artifacts > [] -1, don't rel

[DISCUSS] [VOTE] Release Log4j Audit 1.0.1 RC1

This vote has now been open for 2 1/2 days. Please find the time to review it. I should also note that the Kotlin vote has been open for over a month now. Please review that as well. Ralph > On Dec 2, 2018, at 8:42 PM, Ralph Goers wrote: > > This is a vote to release Log4j-Au

Re: [VOTE] Release Log4j Audit 1.0.1 RC1

: > This is a vote to release Log4j-Audit 1.0.1, the second release of the > Log4j Audit project. > > Please download, test, and cast your votes on the log4j developers list. > [] +1, release the artifacts > [] -1, don't release because... > > The vote will remain open for

[VOTE] Release Log4j Audit 1.0.1 RC1

This is a vote to release Log4j-Audit 1.0.1, the second release of the Log4j Audit project. Please download, test, and cast your votes on the log4j developers list. [] +1, release the artifacts [] -1, don't release because... The vote will remain open for 72 hours (or more if required)

Re: [ANNOUNCE] Apache Log4j Audit 1.0.0 released

(Re-posting since I did not see the link when sending from my yahoo mail account.) Blogged: https://blogs.apache.org/logging/entry/announce-apache-log4j-audit-1 Please share on social media! Thanks, -Remko On Mon, Jun 25, 2018 at 7:48 PM, Remko Popma wrote: > Blogged: [ANNOUNCE] Apache Lo

Re: [ANNOUNCE] Apache Log4j Audit 1.0.0 released

Blogged: [ANNOUNCE] Apache Log4j Audit 1.0.0 released : Apache Logging Services | | | | [ANNOUNCE] Apache Log4j Audit 1.0.0 released : Apache Logging Services | | | Please share on social media! Thanks,-Remko On Saturday, June 23, 2018, 1:31:26 AM GMT+9, Matt Sicker wrote

Re: [ANNOUNCE] Apache Log4j Audit 1.0.0 released

i.info > > > On Jun 23, 2018, at 0:39, Ralph Goers > wrote: > > > > The Apache Log4j team is pleased to announce the Apache Log4j Audit > 1.0.0 release! > > > > Apache Log4j Audit provides a framework for defining audit events and > then logging them

Re: [ANNOUNCE] Apache Log4j Audit 1.0.0 released

I should be able to blog this announcement tomorrow morning but now it’s bedtime for me. :-) (Shameless plug) Every java main() method deserves http://picocli.info > On Jun 23, 2018, at 0:39, Ralph Goers wrote: > > The Apache Log4j team is pleased to announce the Apache Log4j Au

Re: [ANNOUNCE] Apache Log4j Audit 1.0.0 released

Being a 1.0 release, I think this should also be posted to announce@ as well as maybe a press release? :) On 22 June 2018 at 10:39, Ralph Goers wrote: > The Apache Log4j team is pleased to announce the Apache Log4j Audit 1.0.0 > release! > > Apache Log4j Audit provides a framework

[ANNOUNCE] Apache Log4j Audit 1.0.0 released

The Apache Log4j team is pleased to announce the Apache Log4j Audit 1.0.0 release! Apache Log4j Audit provides a framework for defining audit events and then logging them using Log4j. The framework focuses on defining the events and providing an easy mechanism for applications to log them

Re: [VOTE] Release Log4j Audit 1.0.0 RC1

I’m not sure I was clear. Log4j Audit does not provide a UI to view audit events. It provides the catalog so anyone implementing a UI can do so. Ultimately, Log4j Audit is sending Structured Data Messages through Log4j. Log4j can be configured to deliver them anywhere, including Splunk, an SIEM

Re: [VOTE] Release Log4j Audit 1.0.0 RC1

;>> On Jun 21, 2018, at 8:12 AM, Matt Sicker wrote: > >>>> > >>>> Also just noticed the "getting started" link in the intro paragraph > is a > >>>> dead link. The sidebar link is correct, though. > >>>> > >>&

Re: [VOTE] Release Log4j Audit 1.0.0 RC1

e "getting started" link in the intro paragraph is a >>>> dead link. The sidebar link is correct, though. >>>> >>>> On 21 June 2018 at 10:11, Matt Sicker wrote: >>>> >>>>> Looks like we forgot an htaccess redirect here: http://logging.apa

Re: [VOTE] Release Log4j Audit 1.0.0 RC1

>> Also just noticed the "getting started" link in the intro paragraph is a > >> dead link. The sidebar link is correct, though. > >> > >> On 21 June 2018 at 10:11, Matt Sicker wrote: > >> > >>> Looks like we forgot an htaccess redirect h

Re: [VOTE] Release Log4j Audit 1.0.0 RC1

er wrote: >> >> Also just noticed the "getting started" link in the intro paragraph is a >> dead link. The sidebar link is correct, though. >> >> On 21 June 2018 at 10:11, Matt Sicker wrote: >> >>> Looks like we forgot an htaccess redirect h

Re: [VOTE] Release Log4j Audit 1.0.0 RC1

ink is correct, though. > > On 21 June 2018 at 10:11, Matt Sicker wrote: > >> Looks like we forgot an htaccess redirect here: http://logging.apache. >> org/log4j-audit/ >> >> On 18 June 2018 at 03:32, Remko Popma wrote: >> >>> It’s the one ca

Re: [VOTE] Release Log4j Audit 1.0.0 RC1

Also just noticed the "getting started" link in the intro paragraph is a dead link. The sidebar link is correct, though. On 21 June 2018 at 10:11, Matt Sicker wrote: > Looks like we forgot an htaccess redirect here: http://logging.apache. > org/log4j-audit/ > > On 18 Jun

Re: [VOTE] Release Log4j Audit 1.0.0 RC1

Looks like we forgot an htaccess redirect here: http://logging.apache.org/log4j-audit/ On 18 June 2018 at 03:32, Remko Popma wrote: > It’s the one called logo.jpg. > All png logo files are our modified versions AFAICS. > > > > On Jun 18, 2018, at 13:08, Ralph Goers > wrote

Re: [VOTE] Release Log4j Audit 1.0.0 RC1

It’s the one called logo.jpg. All png logo files are our modified versions AFAICS. > On Jun 18, 2018, at 13:08, Ralph Goers wrote: > > I’m OK with that, assuming I can remember which one it was. > > Ralph > >> On Jun 17, 2018, at 3:53 PM, Remko Popma wrote: >> >> About the logo: I would p

Re: [VOTE] Release Log4j Audit 1.0.0 RC1

I’m OK with that, assuming I can remember which one it was. Ralph > On Jun 17, 2018, at 3:53 PM, Remko Popma wrote: > > About the logo: I would prefer that everywhere we use it we stick to the > Log4j 2 logo as it was designed and not change the colors or pattern any > more. > > The origina

Re: [VOTE] Release Log4j Audit 1.0.0 RC1

About the logo: I would prefer that everywhere we use it we stick to the Log4j 2 logo as it was designed and not change the colors or pattern any more. The original looks much more clean and professional. > On Jun 18, 2018, at 2:06, Ralph Goers wrote: > > Thanks Matt! > > Any help you want

[RESULT][VOTE] Release Log4j Audit 1.0.0 RC1

This vote passes with +1 votes from Remko Popma, Ralph Goers and Matt Sicker. I will continue with the release process, including tying it into the logging web site. Ralph

Re: [VOTE] Release Log4j Audit 1.0.0 RC1

Thanks Matt! Any help you want to provide would of course be welcome! If you have ideas on how to improve the documentation please go for it! As for the Log4j logo, I didn’t see any reason not to use it and didn’t really want to spend the time creating a new one. Ralph > On Jun 17, 2018, at 9

Re: Reminder - [VOTE] Release Log4j Audit 1.0.0 RC1

gt;> >> >>>>>> On Jun 14, 2018, at 7:58 AM, Matt Sicker wrote: >> >>>>>> >> >>>>>> I'll be back home tomorrow where I have computers set up for >> testing >> >>>> Apache >> >>>

Re: [VOTE] Release Log4j Audit 1.0.0 RC1

+1 Notes: * The git checkout command only worked for me without the "tags/" prefix to the tag name, not sure why. * If you change the wget command to use --cut-dirs=5, you can use the same command with the dist.a.o URL, pretty handy for verifying the artifacts * I recently discovered you can use

Re: Reminder - [VOTE] Release Log4j Audit 1.0.0 RC1

ache > >>>>>> releases. > >>>>>> > >>>>>>> On 12 June 2018 at 22:10, Remko Popma > wrote: > >>>>>>> > >>>>>>> +1 > >>>>>>> > >>>>>>> (Shameless p

Re: Reminder - [VOTE] Release Log4j Audit 1.0.0 RC1

>>>> +1 >>>>>>> >>>>>>> (Shameless plug) Every java main() method deserves >> http://picocli.info >>>>>>> >>>>>>>> On Jun 13, 2018, at 9:03, Gary Gregory >>>> wrote: >>>>>>>&

Re: Reminder - [VOTE] Release Log4j Audit 1.0.0 RC1

gt; >>>>> > >>>>>> On Jun 13, 2018, at 9:03, Gary Gregory > >> wrote: > >>>>>> > >>>>>> I started reading the site, which is good so far... should be able > to > >>>>>> continue tomor

Re: Reminder - [VOTE] Release Log4j Audit 1.0.0 RC1

ted reading the site, which is good so far... should be able to >>>>>> continue tomorrow... >>>>>> >>>>>> Gary >>>>>> >>>>>>> On Tue, Jun 12, 2018, 17:35 Ralph Goers >>>>> wrote: >>>>>&

  1   2   >