On 4 February 2018 at 23:35, Ralph Goers <ralph.go...@dslextreme.com> wrote:
> Well I have good news and bad news. The bad news is that I forgot my wife > and I were having people over for the super bowl so I didn’t have as much > time as I had hoped and I wasn’t able to run the Log4j 2.11.0 release build. > No worries! > The good news is that I think Log4j Audit V1.0 is about ready for a > release. I have published the web site at https://rgoers.github.io/ > log4j-audit/index.html <https://rgoers.github.io/log4j-audit/index.html>. > Some parts of the site will have problems since it hasn’t been released but > I hope you could take a look at it and review it before a release vote is > attempted. > Awesome! I'm not too familiar with audit logging, so I'll have feedback from that point of view. I haven't used Spring in several months, but one of the last things I worked on in that realm was a similar project to Brave/Zipkin, so I'm at least familiar with per-request logging and tracing sorts of things at least (particularly in how to integrate it automatically with Spring via Spring Boot, etc.) -- Matt Sicker <boa...@gmail.com>
