Allow JdbcTelemetry to rely on java opts

[AlixBa]

Is your feature request related to a problem? Please describe.

// opts
-Dotel.instrumentation.jdbc.experimental.capture-query-parameters=true

// and somewhere in the code
JdbcTelemetry.create(otel).wrap(ds)

I think people will expect the opt to be enabled and get data in my spans. But as per the current implementation, JdbcTelemetryBuilder only relies on properties set explicitly such as builder.setCaptureQueryParameters(true).

I see that in OpenTelemetryDataSource there is a deprecated constructor relying on JdbcInstrumenterFactory which allows construction based on the opts. It has been deprecated with introduction of JdbcTelemetry andJdbcTelemetryBuilder.

Describe the solution you'd like

Would it be possible to provide something like JdbcTelemetry.autoConfigured(otel) for this use case or is it something that has been not allowed on purpose?

Describe alternatives you've considered

No response

Additional context

I'd be happy to implement it as soon as we have a solution!

[laurit]

Would it be possible to provide something like JdbcTelemetry.autoConfigured(otel) for this use case or is it something that has been not allowed on purpose?

If something like this were to be implemented it would need to be consistently implemented for all of the library instrumentations. It is unlikely that just using system properties and environment variables is going to cut it as someone is bound to ask for providing configuration through spring properties etc.

[trask]

this should be possible to implement after the next SDK release now that we have an official (incubating) configuration API

(note it won't support java opts, but will support yaml based declarative configuration)

[zeitlinger]

I've already started a PR that uses the next SDK that already configures otel.instrumentation.jdbc.experimental.capture-query-parameters: #14767