Re: Monitoring discards from async logging

2024-04-10 Thread Thomas, Adam
> What version of Java are you using? If it is Java 17 Unfortunately, I need to support Java 8 and 11. > you can still configure Log4j Core to use your own implementation of > `AsyncQueueFullPolicy` by setting the `log4j2.asyncQueueFullPolicy` system > property I would do this if I had control

Re: Monitoring discards from async logging

2024-04-10 Thread Piotr P. Karwasz
Hi Adam, On Wed, 10 Apr 2024 at 19:03, Thomas, Adam wrote: > I would do this if I had control of the end user's logging setup. > Unfortunately, I vend an internal library that is used by a lot of different > teams. By the time my code is invoked, AsyncLoggerDisruptor has already read > the sys

Re: Monitoring discards from async logging

2024-04-10 Thread Thomas, Adam
> All you need is a `log4j2.component.properties` file in your library. It is very common practice here to explicitly specify the discard policy as a system property, as it was recommended to teams moving from log4j1 to log4j2. Adding this would have very little impact. > Until then I am afraid