You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
@Substitute@Overridepublicvoidreport(JaegerSpanspan) {
System.err.println("--- not logging: " + span);
}
Is there a reason for it not simply using a org.jboss.logging.Logger for this, in order to get a proper log instead?
Sorry if this might be an obvious limitation and there's nothing that can be done in regards to this, but it creates a bit of inconsistency amongst our different Quarkus services when they're not reporting spans created the same way (and also making us have to parse non-log-lines).
Implementation ideas
Simply change the io.quarkus.jaeger.runtime.graal.Target_LoggingReporter
@Substitute@Overridepublicvoidreport(JaegerSpanspan) {
System.err.println("--- not logging: " + span);
}
Description
When enabling the log-span reporter for jaeger, the sent spans are reported, but the behaviour differs between native/non-native builds.
When running in java-mode, the LoggingReporter from Jaeger-client is used: https://github.com/jaegertracing/jaeger-client-java/blob/master/jaeger-core/src/main/java/io/jaegertracing/internal/reporters/LoggingReporter.java. It produces the following log-output:
But when running in native-mode:
This is because the https://github.com/quarkusio/quarkus/blob/main/extensions/jaeger/runtime/src/main/java/io/quarkus/jaeger/runtime/graal/Target_LoggingReporter.java is used, which simply writes to stderr instead of a proper log.
Is there a reason for it not simply using a org.jboss.logging.Logger for this, in order to get a proper log instead?
Sorry if this might be an obvious limitation and there's nothing that can be done in regards to this, but it creates a bit of inconsistency amongst our different Quarkus services when they're not reporting spans created the same way (and also making us have to parse non-log-lines).
Implementation ideas
Simply change the io.quarkus.jaeger.runtime.graal.Target_LoggingReporter
into:
using org.jboss.logging.Logger
The text was updated successfully, but these errors were encountered: