IMO metrics and auditing don’t have a lot in common. That said, I do use the
RequestContext to log elapsed time of every request. See the
RequestContextFilter class.
Ralph
> On Jun 11, 2018, at 11:56 AM, Matt Sicker wrote:
>
> What about metrics gathering? Is that an orthogonal concern or ca
What about metrics gathering? Is that an orthogonal concern or can you make
audit logs like that?
On Mon, Jun 11, 2018 at 12:59, Ralph Goers
wrote:
> So for the use case you describe I would suggest you think about the
> events that need to be audited and the data that is associated with those
>
So for the use case you describe I would suggest you think about the events
that need to be audited and the data that is associated with those events. Then
figure out which are request context items (for web apps there are a few that
should be considered “universal" since every app on the planet
That's why I think the site is really important.
More use cases could help people imagine how they could apply this in their
organization.
I work in finance and having an audit trail is mandatory for everything
that modifies the production system.
This often involves deployment scripts and GUIs (w
I think this is an observability related idea which is still rather new to
many companies who are just finally embracing DevOps in the first place. I
love the idea though!
On Mon, Jun 11, 2018 at 10:32, Ralph Goers
wrote:
> Really? I would think almost everything would want to track who made wha
Really? I would think almost everything would want to track who made what
change to the system.
Ralph
> On Jun 11, 2018, at 5:20 AM, Matt Sicker wrote:
>
> Ok, thanks for the clarification. It sounded far more advanced, and I’m
> getting a better picture here. I’ve never worked in a domain th
Ok, thanks for the clarification. It sounded far more advanced, and I’m
getting a better picture here. I’ve never worked in a domain that requires
auditing before.
On Mon, Jun 11, 2018 at 08:03, Apache wrote:
> No. It implements that feature through the request context but I wouldn’t
> use a cat
No. It implements that feature through the request context but I wouldn’t use a
catalog for simple trace logging.
Ralph
> On Jun 11, 2018, at 4:29 AM, Matt Sicker wrote:
>
> One thing I didn’t notice until now is that this is a superset of
> distributed trace logging. Would you say that’s accu
No, still in my bullet journal as to do. This and the Kotlin API releases
are what I’m planning to cover soon, but I’m in process of moving at the
moment and things are a little hectic for now.
On Sun, Jun 10, 2018 at 16:26, Ralph Goers
wrote:
> Did you ever follow up on this? I am still seeing
One thing I didn’t notice until now is that this is a superset of
distributed trace logging. Would you say that’s accurate?
On Mon, Jun 11, 2018 at 00:54, Apache wrote:
> One thing I forgot to mention. Although Log4J audit doesn’t make use of
> the product or category the catalog’s usefulness re
Hi all,
While working on an enterprise software, I bumped into issue LOG4J2-1721 [1]
last week. I took a closer look at the code and have created pull request #176
[2]. Basically, for non-JNDI it allows composite configuration for the
"log4jConfiguration" context parameter.
I have already mail
11 matches
Mail list logo
