Link to parameterized queries from set-up docs (#32528)

* link to parameterized queries from set up docs

* add permission call-out

* Update content/en/database_monitoring/guide/parameterized_queries.md

Co-authored-by: Esther Kim <esther.kim@datadoghq.com>

* change color and fix embedded link

---------

Co-authored-by: Esther Kim <esther.kim@datadoghq.com>
Co-authored-by: cecilia saixue wat-kim <cecilia.watt@datadoghq.com>

Author: 3 people

content/en/database_monitoring/guide/parameterized_queries.md

@@ -1,6 +1,5 @@
 ---
 title: Capturing SQL Query Parameter Values With Database Monitoring
-private: true
 further_reading:
 - link: "/database_monitoring/"
   tag: "Documentation"
@@ -13,10 +12,6 @@ further_reading:
   text: "Troubleshooting Database Monitoring"
 ---
 
-<div class="alert alert-info">
-This feature is in preview. To enable collection of raw SQL query text and execution plans with parameter values, please contact your Datadog representative or support.
-</div>
-
 The Database Monitoring integrations collect aggregated query metrics, in-flight query executions, and query explain plans across your database. By default, query SQL texts and explain plans are obfuscated and normalized in the Agent before being sent to Datadog in order to protect sensitive data, which may be exposed in query parameters.
 
 However, exposing query statements with actual parameter values provides enhanced observability and debugging capabilities. Database Monitoring currently supports query capture with parameter values on the PostgreSQL and SQL Server integrations.
@@ -31,7 +26,7 @@ Having access to query parameters enables:
 
 ## Before you begin
 
-<div class="alert alert-info">Query statements and execution plans with parameterized values may contain sensitive information (for example, passwords in query parameters) or personally identifiable information. Enabling this option allows Datadog to collect and ingest raw query statements and execution plans that appear in query samples or explain plans. This option is disabled by default.</div>
+<div class="alert alert-danger">Query statements and execution plans with parameterized values may contain sensitive information (for example, passwords in query parameters) or personally identifiable information. Enabling this option allows Datadog to collect and ingest raw query statements and execution plans that appear in query samples or explain plans. This option is disabled by default.</div>
 
 You must configure Database Monitoring for your [SQL Server][1] instance before continuing with this guide.
 
@@ -41,6 +36,10 @@ Supported databases
 Supported deployments
 : All deployment types.
 
+## Permissions
+
+To view query parameter values in the Database Monitoring UI, users need the **Database Monitoring Parameterized Queries Read** permission. This permission is located under the **Database Monitoring** section in the [Roles page][2]. This permission is enabled by default in the Datadog Admin Role, Datadog Standard Role, and Datadog Read Only Role. If your organization uses custom roles, add this permission to the appropriate role. For more information on managing permissions, see the [RBAC documentation][3].
+
 ## Setup
 To capture SQL query text and execution plans with parameter values, update the appropriate integration `conf.yaml` file based on your database type:
 - For PostgreSQL: edit `postgres.d/conf.yaml`
@@ -51,7 +50,8 @@ To capture SQL query text and execution plans with parameter values, update the
     enabled: true
 ```
 
-For SQL Server, capturing parameter values from prepared statements requires enabling query completion capture via Extended Events. See [configure your SQL Server instance and integration to capture query completions][1] in order to complete the database set up.
+<div class="alert alert-info">
+For SQL Server, capturing parameter values from prepared statements requires enabling query completion capture through Extended Events. See <a href="/database_monitoring/guide/sql_extended_events/">configure your SQL Server instance and integration to capture query completions</a> in order to complete the database set up. </div>
 
 ```yaml
   xe_collection:
@@ -92,3 +92,5 @@ To capture prepared statements with parameter values in SQL Server, you must [co
 Support for PostgreSQL prepared statement parameter value capture is not available at this time.
 
 [1]: /database_monitoring/guide/sql_extended_events/
+[2]: /account_management/rbac/permissions/
+[3]: /account_management/rbac/

content/en/database_monitoring/setup_postgres/alloydb.md

@@ -5,6 +5,9 @@ further_reading:
 - link: "/integrations/postgres/"
   tag: "Documentation"
   text: "Basic Postgres Integration"
+- link: "/database_monitoring/guide/parameterized_queries/"
+  tag: "Documentation"
+  text: "Capturing SQL Query Parameter Values"
 ---
 
 Database Monitoring provides deep visibility into your Postgres databases by exposing query metrics, query samples, explain plans, database states, failovers, and events.
@@ -274,7 +277,7 @@ Using the [Operator instructions in Kubernetes and Integrations][3] as a referen
     ```shell
     kubectl apply -f datadog-agent.yaml
     ```
-  
+
 ### Helm
 
 Using the [Helm instructions in Kubernetes and Integrations][4] as a reference, follow the steps below to set up the Postgres integration:

content/en/database_monitoring/setup_postgres/aurora.md

@@ -5,6 +5,9 @@ further_reading:
 - link: "/integrations/postgres/"
   tag: "Documentation"
   text: "Basic Postgres Integration"
+- link: "/database_monitoring/guide/parameterized_queries/"
+  tag: "Documentation"
+  text: "Capturing SQL Query Parameter Values"
 ---
 
 Database Monitoring provides deep visibility into your Postgres databases by exposing query metrics, query samples, explain plans, database states, failovers, and events.

content/en/database_monitoring/setup_postgres/azure.md

@@ -5,6 +5,9 @@ further_reading:
 - link: "/integrations/postgres/"
   tag: "Documentation"
   text: "Basic Postgres Integration"
+- link: "/database_monitoring/guide/parameterized_queries/"
+  tag: "Documentation"
+  text: "Capturing SQL Query Parameter Values"
 ---
 
 Database Monitoring provides deep visibility into your Postgres databases by exposing query metrics, query samples, explain plans, database states, failovers, and events.

content/en/database_monitoring/setup_postgres/gcsql.md

@@ -5,6 +5,9 @@ further_reading:
 - link: "/integrations/postgres/"
   tag: "Documentation"
   text: "Basic Postgres Integration"
+- link: "/database_monitoring/guide/parameterized_queries/"
+  tag: "Documentation"
+  text: "Capturing SQL Query Parameter Values"
 ---
 
 Database Monitoring provides deep visibility into your Postgres databases by exposing query metrics, query samples, explain plans, database states, failovers, and events.
@@ -273,7 +276,7 @@ Using the [Operator instructions in Kubernetes and Integrations][3] as a referen
     ```shell
     kubectl apply -f datadog-agent.yaml
     ```
-  
+
 ### Helm
 
 Using the [Helm instructions in Kubernetes and Integrations][4] as a reference, follow the steps below to set up the Postgres integration:

content/en/database_monitoring/setup_postgres/heroku.md

@@ -7,6 +7,9 @@ further_reading:
 - link: "/agent/basic_agent_usage/heroku/"
   tag: "Documentation"
   text: "Datadog Heroku Buildpack"
+- link: "/database_monitoring/guide/parameterized_queries/"
+  tag: "Documentation"
+  text: "Capturing SQL Query Parameter Values"
 ---
 
 This guide assumes that you have configured the [Datadog Heroku buildpack][1] in your application dynos.
@@ -89,7 +92,7 @@ heroku config:set DD_ENABLE_HEROKU_POSTGRES=true
 git commit --allow-empty -m "enabled postgres integration"
 git push heroku main
 ```
- 
+
 To enable both the Postgres integration and Database Monitoring, set `DD_ENABLE_HEROKU_POSTGRES` and `DD_ENABLE_DBM` to true:
 
 ``` shell
@@ -140,7 +143,7 @@ In the root of the project, create a directory for the Postgres configuration ca
 mkdir -p datadog/conf.d/postgres.d
 touch datadog/conf.d/postgres.d/conf.yaml
 ```
- 
+
 Add the following to `conf.yaml`:
 
 ``` yaml
@@ -217,4 +220,3 @@ The database connection is now configured. To enable additional features, such a
 [4]: https://devcenter.heroku.com/articles/heroku-postgres-plans
 [6]: /database_monitoring/schema_explorer
 [7]: https://github.com/DataDog/integrations-core/blob/master/postgres/datadog_checks/postgres/data/conf.yaml.example
- 

content/en/database_monitoring/setup_postgres/rds/_index.md

@@ -8,6 +8,9 @@ further_reading:
 - link: "/database_monitoring/guide/rds_autodiscovery"
   tag: "Documenation"
   text: "Autodiscovery for RDS"
+- link: "/database_monitoring/guide/parameterized_queries/"
+  tag: "Documentation"
+  text: "Capturing SQL Query Parameter Values"
 ---
 
 Database Monitoring provides deep visibility into your Postgres databases by exposing query metrics, query samples, explain plans, database states, failovers, and events.

content/en/database_monitoring/setup_postgres/selfhosted.md

@@ -5,6 +5,9 @@ further_reading:
 - link: "/integrations/postgres/"
   tag: "Documentation"
   text: "Basic Postgres Integration"
+- link: "/database_monitoring/guide/parameterized_queries/"
+  tag: "Documentation"
+  text: "Capturing SQL Query Parameter Values"
 ---
 
 Database Monitoring provides deep visibility into your Postgres databases by exposing query metrics, query samples, explain plans, database states, failovers, and events.

content/en/database_monitoring/setup_sql_server/azure.md

@@ -14,6 +14,9 @@ further_reading:
 - link: "/database_monitoring/guide/sql_extended_events/"
   tag: "Documentation"
   text: "Configure Query Completion and Query Error Collection"
+- link: "/database_monitoring/guide/parameterized_queries/"
+  tag: "Documentation"
+  text: "Capturing SQL Query Parameter Values"
 ---
 
 Database Monitoring provides deep visibility into your Microsoft SQL Server databases by exposing query metrics, query samples, explain plans, database states, failovers, and events.

content/en/database_monitoring/setup_sql_server/gcsql.md

@@ -11,6 +11,9 @@ further_reading:
 - link: "/database_monitoring/guide/sql_extended_events/"
   tag: "Documentation"
   text: "Configure Query Completion and Query Error Collection"
+- link: "/database_monitoring/guide/parameterized_queries/"
+  tag: "Documentation"
+  text: "Capturing SQL Query Parameter Values"
 ---
 
 Database Monitoring provides deep visibility into your Microsoft SQL Server databases by exposing query metrics, query samples, explain plans, database states, failovers, and events.