Add read-only user best practice recommendation to integration READMEs (DataDog#22778)

Author: coignetp

clickhouse/README.md

@@ -16,6 +16,10 @@ The ClickHouse check is included in the [Datadog Agent][3] package. No additiona
 
 ### Configuration
 
+#### Prepare ClickHouse
+
+As a best practice, Datadog recommends using a read-only user to monitor your ClickHouse instance. This limits the access granted to the Datadog Agent.
+
 <!-- xxx tabs xxx -->
 <!-- xxx tab "Host" xxx -->
 

cloudera/README.md

@@ -21,6 +21,9 @@ No additional installation is needed on your server.
 The Cloudera check requires version 7 of Cloudera Manager.
 
 #### Prepare Cloudera Manager
+
+As a best practice, Datadog recommends creating the machine user with read-only access to limit the permissions granted to the Datadog Agent.
+
 1. In Cloudera Data Platform, navigate to the Management Console and click on the **User Management** tab.
 ![User Management][10]
 

foundationdb/README.md

@@ -21,6 +21,10 @@ but requires the [FoundationDB client][8] to be installed.
 
 ### Configuration
 
+#### Prepare FoundationDB
+
+As a best practice, Datadog recommends using a read-only user to monitor your FoundationDB cluster. This limits the access granted to the Datadog Agent.
+
 <!-- xxx tabs xxx -->
 <!-- xxx tab "Host" xxx -->
 

ibm_was/README.md

@@ -36,6 +36,10 @@ Once you've made this change, click "Apply" to save the configuration and restar
 
 ### Configuration
 
+#### Prepare IBM WAS
+
+As a best practice, Datadog recommends using a read-only user to monitor your IBM WAS instance. This limits the access granted to the Datadog Agent.
+
 <!-- xxx tabs xxx -->
 <!-- xxx tab "Host" xxx -->
 

openldap/README.md

@@ -19,6 +19,8 @@ The OpenLDAP integration is packaged with the Agent. To start gathering your Ope
 
 #### Prepare OpenLDAP
 
+The user created in these steps is granted read-only access to the monitor backend. As a best practice, Datadog recommends this read-only setup to limit the permissions granted to the Datadog Agent.
+
 If the `cn=Monitor` backend is not configured on your server, follow these steps:
 
 1. Check if monitoring is enabled on your installation:

singlestore/README.md

@@ -22,6 +22,10 @@ No additional installation is needed on your server.
 
 ### Configuration
 
+#### Prepare SingleStore
+
+As a best practice, Datadog recommends using a read-only user to monitor your SingleStore instance. This limits the access granted to the Datadog Agent.
+
 #### Host
 
 ##### Metric collection

snowflake/README.md

@@ -29,6 +29,8 @@ The Snowflake check is included in the [Datadog Agent][2] package.
 ### Configuration
 <div class="alert alert-warning">Snowflake recommends granting permissions to an alternate role like `SYSADMIN`. Read more about controlling <a href="https://docs.snowflake.com/en/user-guide/security-access-control-considerations.html#control-the-assignment-of-the-accountadmin-role-to-users">ACCOUNTADMIN role</a> for more information.</div>
 
+As a best practice, Datadog recommends creating a dedicated role and user with read-only access to monitor your Snowflake instance. This limits the access granted to the Datadog Agent.
+
 1. Create a Datadog specific role and user to monitor Snowflake. In Snowflake, run the following to create a custom role with access to the ACCOUNT_USAGE schema.
 
     Note: By default, this integration monitors the `SNOWFLAKE` database and `ACCOUNT_USAGE` schema. See "Collecting Organization Data" for information on how to monitor the `ORGANIZATION_USAGE` schema.