Using Slf4J instead of Jboss Logger

[estet90]

Description

Now Jboss Logger is used everywhere in the Quarkus libraries. If I want to use a Log4J2 in my projects and send logs through it, for example, TCP, Quarkus logs do not get into the log collection system. Is it possible to do it by analogy with Spring, using Slf4J in the libraries, so that the developer himself can determine the implementation?

Implementation ideas

No response

[geoand]

As is mentioned in the docs, you can use slf4j as the logging API.
What Quarkus mandates is the use of JBoss Logging Manager as the implementation - i.e. you can't use Logback or Log4j2.

[estet90]

As is mentioned in the docs, you can use slf4j as the logging API. What Quarkus mandates is the use of JBoss Logging Manager as the implementation - i.e. you can't use Logback or Log4j2.

You did not understand me. I want to forward quarkus logs such as "service start logs" to log4j2, and then I could send them anywhere.

[geoand]

What'l does forward logs to Log4j2 mean?
As I explained, we won't be supporting it.

We do however have various transport mechanisms for JBoss Logmanager