Disable db.statement via instrumentation configuration

CHANGELOG.md

@@ -26,7 +26,7 @@ release.
 - Add details for filling resource for AWS Lambda. ([#1610](https://github.com/open-telemetry/opentelemetry-specification/pull/1610))
 - Add already specified `messaging.rabbitmq.routing_key` span attribute key to the respective YAML file.
 - Clarify usage of "otel." attribute namespace. ([#1640](https://github.com/open-telemetry/opentelemetry-specification/pull/1640))
-- Add possibility to disable `db.statement`. ([#1659](https://github.com/open-telemetry/opentelemetry-specification/pull/1659))
+- Add possibility to disable `db.statement` via instrumentation configuration. ([#1659](https://github.com/open-telemetry/opentelemetry-specification/pull/1659))
 
 ### Compatibility
 

semantic_conventions/trace/database.yaml

@@ -185,7 +185,7 @@ groups:
           type: string
           required:
             conditional: >
-              Required if applicable or not explicitly disabled.
+              Required if applicable or not explicitly disabled via instrumentation configuration.
           brief: >
             The database statement being executed.
           note: The value may be sanitized to exclude sensitive information.

specification/trace/semantic_conventions/database.md

@@ -155,7 +155,7 @@ Usually only one `db.name` will be used per connection though.
 
 **[3]:** The value may be sanitized to exclude sensitive information.
 
-**[4]:** Required if applicable or not explicitly disabled.
+**[4]:** Required if applicable or not explicitly disabled via instrumentation configuration.
 
 **[5]:** When setting this to an SQL keyword, it is not recommended to attempt any client-side parsing of `db.statement` just to get this property, but it should be set if the operation name is provided by the library being instrumented. If the SQL statement has an ambiguous operation, or performs more than one operation, this value may be omitted.
 <!-- endsemconv -->