Thanks for the clarification Ralph.
I understand the rationale for unix logs. I believe we should reassess this
default for the following reasons:
- Users rarely feed service app logs to system logs. Those who do,
simply ingest lines intact without any timestamp prefixing.
- I have never
Can -slf4j18-impl users simply upgrade to -slf4j20-impl without any changes
except replacing the relevant dependency?
On Fri, Aug 26, 2022 at 9:55 PM Ralph Goers
wrote:
> Ceki never released a GA version of SLF4J 1.8. Since we are adding
> support for SLF4J 2.0 in the next release I would sugge
Hi Volkan,
On Sun, 28 Aug 2022 at 21:35, Volkan Yazıcı wrote:
>
> Can -slf4j18-impl users simply upgrade to -slf4j20-impl without any changes
> except replacing the relevant dependency?
Are you talking about Maven redirection? Sounds good to me.
Piotr
> On Aug 27, 2022, at 3:00 AM, Piotr P. Karwasz wrote:
>
> On Fri, 26 Aug 2022 at 21:55, Ralph Goers wrote:
>> Ceki never released a GA version of SLF4J 1.8. Since we are adding support
>> for SLF4J 2.0 in the next release I would suggest we also remove
>> log4j-slf4j18-impl.
>
> I agree.
Hi Ralph,
On Tue, 23 Aug 2022 at 08:14, Ralph Goers wrote:
> I don’t see that as a problem at all. Log4jLogEvent’s constructor accepts a
> List of properties. We use this to inject properties configured on Loggers
> into the Context Map of the LogEvent. I see no reason why these key/value
> pa
You seem to be forgetting that StatusLogger doesn’t use Log4j Core. It
doesn’t write to rotated logs and cannot write to anything over the network.
It only supports specifying a simple file name.
At work, all my services use Spring Boot. They are configures with a
default log4j2.yml that logs t
