Add additional context for database_identifier configuration for Postgres, MySQL, and SQLServer (DataDog#21575)

* Add additional context for  configuration for Postgres, MySQL, and SQLServer

* Copy

* Changelog

* Copy

Author: sethsamuel

mysql/assets/configuration/spec.yaml

@@ -79,8 +79,10 @@ files:
             default: false
           - name: database_identifier
             description: |
-              Controls how the database is identified. The default value is the resolved hostname for the instance,
-              which respects the `reported_hostname` option.
+              Controls how the database is identified. Each unique value of this identifier will appear in DBM as a separate
+              billable instance.
+              
+              The default value is the resolved hostname for the instance, which respects the `reported_hostname` option.
 
               This value will be used as-is for the display name of the instance but will be normalized
               when applied as the `database_instance` tag. Please see https://docs.datadoghq.com/getting_started/tagging/

mysql/changelog.d/21575.added

@@ -0,0 +1 @@
+Add additional context to the database_identifier configuration description.

mysql/datadog_checks/mysql/data/conf.yaml.example

@@ -69,8 +69,10 @@ instances:
     #
     # exclude_hostname: false
 
-    ## Controls how the database is identified. The default value is the resolved hostname for the instance,
-    ## which respects the `reported_hostname` option.
+    ## Controls how the database is identified. Each unique value of this identifier will appear in DBM as a separate
+    ## billable instance.
+    ##
+    ## The default value is the resolved hostname for the instance, which respects the `reported_hostname` option.
     ##
     ## This value will be used as-is for the display name of the instance but will be normalized
     ## when applied as the `database_instance` tag. Please see https://docs.datadoghq.com/getting_started/tagging/

postgres/assets/configuration/spec.yaml

@@ -58,8 +58,10 @@ files:
         example: false
     - name: database_identifier
       description: |
-        Controls how the database is identified. The default value is the resolved hostname for the instance, 
-        which respects the `reported_hostname` option.
+        Controls how the database is identified. Each unique value of this identifier will appear in DBM as a separate
+        billable instance.
+        
+        The default value is the resolved hostname for the instance, which respects the `reported_hostname` option.
 
         This value will be used as-is for the display name of the instance but will be normalized
         when applied as the `database_instance` tag. Please see https://docs.datadoghq.com/getting_started/tagging/

postgres/changelog.d/21575.added

@@ -0,0 +1 @@
+Add additional context to the database_identifier configuration description.

postgres/datadog_checks/postgres/data/conf.yaml.example

@@ -70,8 +70,10 @@ instances:
     #
     # exclude_hostname: false
 
-    ## Controls how the database is identified. The default value is the resolved hostname for the instance, 
-    ## which respects the `reported_hostname` option.
+    ## Controls how the database is identified. Each unique value of this identifier will appear in DBM as a separate
+    ## billable instance.
+    ##
+    ## The default value is the resolved hostname for the instance, which respects the `reported_hostname` option.
     ##
     ## This value will be used as-is for the display name of the instance but will be normalized
     ## when applied as the `database_instance` tag. Please see https://docs.datadoghq.com/getting_started/tagging/

sqlserver/assets/configuration/spec.yaml

@@ -80,8 +80,10 @@ files:
       default: false
     - name: database_identifier
       description: |
-        Controls how the database is identified. The default value is the resolved hostname for the instance,
-        which respects the `reported_hostname` option.
+        Controls how the database is identified. Each unique value of this identifier will appear in DBM as a separate
+        billable instance.
+
+        The default value is the resolved hostname for the instance, which respects the `reported_hostname` option.
 
         This value will be used as-is for the display name of the instance but will be normalized
         when applied as the `database_instance` tag. Please see https://docs.datadoghq.com/getting_started/tagging/

sqlserver/changelog.d/21575.added

@@ -0,0 +1 @@
+Add additional context to the database_identifier configuration description.

sqlserver/datadog_checks/sqlserver/data/conf.yaml.example

@@ -85,8 +85,10 @@ instances:
     #
     # exclude_hostname: false
 
-    ## Controls how the database is identified. The default value is the resolved hostname for the instance,
-    ## which respects the `reported_hostname` option.
+    ## Controls how the database is identified. Each unique value of this identifier will appear in DBM as a separate
+    ## billable instance.
+    ##
+    ## The default value is the resolved hostname for the instance, which respects the `reported_hostname` option.
     ##
     ## This value will be used as-is for the display name of the instance but will be normalized
     ## when applied as the `database_instance` tag. Please see https://docs.datadoghq.com/getting_started/tagging/