OTel LateBoundSampler logs warning if using Liquibase and JDBC instrumentation

[famod]

Describe the bug

I was irritated by the following message very early during boot and started digging:

WARN  [io.qua.ope.run.tra.LateBoundSampler] (JPA Startup Thread) No Sampler delegate specified, no action taken.

Turns out that when you have JDBC instrumentation and Liquibase migration at startup (using the same datasource and OTEL driver as the rest of the app), the sampler is apparently not set yet, hence the warning.

Expected behavior

No warning from OTEL extension, even if using "startup time features" such as the liquibase extension.

Actual behavior

Warning logged

How to Reproduce?

liquibase-quickstart-with-otel.zip

mvn quarkus:dev

Output of uname -a or ver

No response

Output of java -version

No response

GraalVM version (if different from Java)

No response

Quarkus version or git rev

2.15.0.Final

Build tool (ie. output of mvnw --version or gradlew --version)

No response

Additional information

LateBoundBatchSpanProcessor issues a similar warning (if otlp export is not disabled).

Of course it doesn't make much sense to trace liquibase JDBC operations, but simply using the regular app datasource is the default setup for simple cases.

[quarkus-bot]

/cc @andrejpetras(liquibase), @geoand(liquibase), @gsmet(liquibase)

[famod]

I think this has more to do with tracing, cc @brunobat @radcortez

[brunobat]

Hi @famod can you please provide a reproducer?

[famod]

Hi @brunobat, I added a reproducer. AFAICS, this issue is not specific to dev mode, but it was the fastest way to reproduce.

The reproducer is basically identical to the official liquibase quickstart, only with two added OTel deps and two additional config settings.

[brunobat]

Thanks very much @famod

[geoand]

In more recent versions of Quarkus, the warning is always displayed when OpenTelemetry is used (regardless of what other extension or configuration are used).

I am looking into a fix

[geoand]

Here it is.