Specifying log level for OpenTelemetry logging

[Ultranium]

I am experimenting with the quarkus-opentelemetry extension and I can't find a way to specify a logging level for the OTLP log exporter.
It is not described in the OpenTelemetry Logging Guide nor in the OpenTelemetry Configuration Reference. Looking through the source code, the quarkus.otel.logs.* configuration branch seems to have only enabled/disabled settings.
A naive approach of setting the quarkus.log.handler.otel.level config property didn't work.

Is it possible to specify the OpenTelemetry logging level at all at this moment?

[quarkus-bot[bot]]

/cc @brunobat (opentelemetry), @radcortez (opentelemetry)

[brunobat]

@Ultranium, OpenTelemetry logging just handles existing logs and enriches them. It is not a new logging framework.
You must tweak the log level at the logging library level to achieve that.
See: https://quarkus.io/guides/logging#use-log-levels

[Ultranium]

@brunobat yes, I know that.

But in Quarkus, it is possible to specify different logging levels for different loggers. For example, I can set DEBUG level for console output while keeping logs exported to syslog at WARN to avoid bloating the centralized log storage with tons of insignificant records using this config:

quarkus.log.syslog.level=WARN
quarkus.log.console.level=DEBUG

So, is it possible to limit the minimum level of logs that are exported via OTLP without changing the ROOT logger level, like it's done with syslog, GELF and other log handlers?
It doesn't seem that OTLP exporter is presented as a separate log handler.

[brunobat]

It uses this log handler:

quarkus/extensions/opentelemetry/runtime/src/main/java/io/quarkus/opentelemetry/runtime/logs/OpenTelemetryLogHandler.java

Line 33 in 80e4bc6

public class OpenTelemetryLogHandler extends ExtHandler {

We can in theory filter out according to log levels in there, even if the spec doesn't define any of that.

[Ultranium]

It uses this log handler:

quarkus/extensions/opentelemetry/runtime/src/main/java/io/quarkus/opentelemetry/runtime/logs/OpenTelemetryLogHandler.java

Line 33 in 80e4bc6

public class OpenTelemetryLogHandler extends ExtHandler {

OK, I must've been missed it.

We can in theory filter out according to log levels in there, even if the spec doesn't define any of that.

It would be really nice. For example, the quarkus-logging-gelf extension, which I am to replace with quarkus-opentelemetry, does implement this level filtering, just like most of other log handlers.

[dmlloyd]

We can in theory filter out according to log levels in there, even if the spec doesn't define any of that.

Since it extends ExtHandler, it has a setLevel(xxx) method, so you can use the same logging config mechanism that is used by e.g. ConsoleConfig or FileConfig (look at LoggingSetupRecorder for an example).