Enhance database reporting config

[dyladan]

Currently there is a config option named enhancedDatabaseReporting that is used by no plugins and is undocumented.

Should we keep the enhanced database reporting config

Since it currently does nothing and is undocumented, is it even worth keeping around?

If we do keep it, what should it do?

There are multiple database plugins (mysql, pg/pg-pool, mongodb-core) and there will likely be others. If we keep this config option, it should do the same thing for all db plugins

[pauldraper]

If it's not used delete it.

Though two cents: plugins ought define separate interfaces with specific options.

new PgOpentelemetryPlugin({ enhancedReporting: true })

[dyladan]

Though two cents: plugins ought define separate interfaces with specific options.

Yes this is the idea behind the new Instrumentation base. The old one unfortunately wasn't very flexible from a config/setup standpoint, but the new one will work exactly as you suggest here.

[vmarchaud]

Apparently this has been discused at the spec level "recently": open-telemetry/opentelemetry-specification#1659

[pichlermarc]

closing as this is not applicable to this repo anymore.