Addressing review comments from PR #5017

Author: chetanchoudhary-sumo

docs/integrations/amazon-aws/dynamodb.md

@@ -107,12 +107,12 @@ Namespace for **Amazon DynamoDB** Service is **AWS/DynamoDB**.
 2. Click **Save**.
 
 
-### Fields in Sumo Logic
+### Configure fields in Sumo Logic
 
-Following fields will always be created automatically as a part of app installation process:
+As part of the app installation process, the following fields will created by default:
 * `tablename`
 
-For information on setting up fields, see [Sumo Logic Fields](/docs/manage/fields).
+To learn more about setting up fields, refer to [Sumo Logic Fields](/docs/manage/fields).
 
 ### Field Extraction Rule(s)
 

docs/integrations/databases/cassandra.md

@@ -28,9 +28,9 @@ The Sumo Logic app for Cassandra supports metrics generated by the [Jolokia2 plu
 This section provides instructions for configuring log and metric collection for the Sumo Logic app for Cassandra.
 
 
-### Step 1: Fields in Sumo Logic
+### Step 1: Configure fields in Sumo Logic
 
-Following fields will always be created automatically as a part of app installation process:
+As part of the app installation process, the following fields will created by default:
 * `component`
 * `environment`
 * `db_system`
@@ -39,15 +39,15 @@ Following fields will always be created automatically as a part of app installat
 * `db_cluster_address`
 * `db_cluster_port`
 
-If you're using Cassandra in a Kubernetes environment, these additional fields will get created automatically as a part of app installation process:
+Additionally, if you are using Redis in the Kubernetes environment, these following additional fields will be created by default as a part of the app installation process:
 * `pod_labels_component`
 * `pod_labels_environment`
 * `pod_labels_db_system`
 * `pod_labels_db_cluster`
 * `pod_labels_db_cluster_address`
 * `pod_labels_db_cluster_port`
 
-For information on setting up fields, see [Sumo Logic Fields](/docs/manage/fields).
+To learn more about setting up fields, refer to [Sumo Logic Fields](/docs/manage/fields).
 
 ### Step 2: Configure Collection for Cassandra
 
@@ -246,7 +246,9 @@ Pivoting to Tracing data from Entity Inspector is possible only for “Cassandra
    5. Sumo Logic Kubernetes collection will automatically start collecting logs from the pods having the annotations defined above.
    6. Verify logs in Sumo Logic.
 
-3. **FER to normalize the fields in Kubernetes environments.** Labels created in Kubernetes environments automatically are prefixed with pod_labels. To normalize these for our app to work, we will have Field Extraction Rule automatically created for Database Application Components named as **AppObservabilityCassandraDatabaseFER**.
+
+<br/>**FER to normalize the fields in Kubernetes environments.** Labels created in Kubernetes environments automatically are prefixed with pod_labels. To normalize these for our app to work, we will have Field Extraction Rule automatically created for Database Application Components named as **AppObservabilityCassandraDatabaseFER**.
+<br/>
 
 </TabItem>
 <TabItem value="non-k8s">
@@ -621,13 +623,20 @@ Use this dashboard to:
 
 ## Create monitors for Cassandra app
 
+Sumo Logic provides pre-configured alerts available through [Sumo Logic monitors](/docs/alerts/monitors) to help you proactively determine if an Cassandra cluster is available and performing as expected. These monitors are based on metric and log data and include pre-set thresholds that reflect industry best practices and recommendations. For more information about individual alerts, refer to the [Cassandra Alerts](/docs/integrations/databases/cassandra#cassandra-alerts).
+
 import CreateMonitors from '../../reuse/apps/create-monitors.md';
 
 <CreateMonitors/>
 
+:::note
+- Ensure that you have [Manage Monitors role capability](/docs/manage/users-roles/roles/role-capabilities/#alerting) permissions to install the Cassandra Alerts.
+- You can only enable the set number of alerts. For more information, refer to [Monitors](/docs/alerts/monitors/create-monitor).
+:::
+
+
 ### Cassandra Alerts
 
-Sumo Logic has provided out-of-the-box alerts available via [Sumo Logic monitors](/docs/alerts/monitors) to help you quickly determine if the Cassandra cluster is available and performing as expected.
 
 | Alert Name         | Alert Description         | Alert Condition | Recover Condition |
 |:-----------|:--------------|:-----------|:------------|

docs/integrations/databases/couchbase.md

@@ -27,23 +27,23 @@ Telegraf 1.14 default of Kubernetes Collection will not work.
 
 This section provides instructions for configuring log and metric collection for the Sumo Logic app for Couchbase.
 
-### Step 1: Fields in Sumo Logic
+### Step 1: Configure fields in Sumo Logic
 
-Following fields will always be created automatically as a part of app installation process:
+As part of the app installation process, the following fields will created by default:
 * `component`
 * `environment`
 * `db_system`
 * `db_cluster`
 * `pod`
 
-If you're using Couchbase in a Kubernetes environment, these additional fields will get created automatically as a part of app installation process:
+Additionally, if you are using Redis in the Kubernetes environment, these following additional fields will be created by default as a part of the app installation process:
 * `pod_labels_component`
 * `pod_labels_environment`
 * `pod_labels_db_system`
 * `pod_labels_db_cluster`
 
 
-For information on setting up fields, see [Sumo Logic Fields](/docs/manage/fields).
+To learn more about setting up fields, refer to [Sumo Logic Fields](/docs/manage/fields).
 
 ### Step 2: Configure Collection for Couchbase
 
@@ -182,7 +182,9 @@ This section explains the steps to collect Couchbase logs from a Kubernetes envi
     ```
    5. Sumo Logic Kubernetes collection will automatically start collecting logs from the pods having the annotations defined above.
    6. Verify logs in Sumo Logic.
-3. **FER to normalize the fields in Kubernetes environments.** Labels created in Kubernetes environments automatically are prefixed with pod_labels. To normalize these for our app to work, we will have Field Extraction Rule automatically created for Database Application Components named as **AppObservabilityCouchbaseDatabaseFER**.
+
+<br/>**FER to normalize the fields in Kubernetes environments.** Labels created in Kubernetes environments automatically are prefixed with pod_labels. To normalize these for our app to work, we will have Field Extraction Rule automatically created for Database Application Components named as **AppObservabilityCouchbaseDatabaseFER**.
+<br/>
 
 </TabItem>
 <TabItem value="non-k8s">
@@ -456,7 +458,7 @@ The **Couchbase -  Events** dashboard provides insights into events from couchba
 Use this dashboard to:
 * To audit the activities happening in the cluster. This helps to determine what activities have occurred in the system, helping to control system security.
 
-<img src={useBaseUrl('img/integrations/databases/Couchbase-Events.png')} alt="Cassandra dashboards" />
+<img src={useBaseUrl('img/integrations/databases/Couchbase-Events.png')} alt="Couchbase dashboards" />
 
 ### HTTP Access
 
@@ -465,14 +467,21 @@ The **Couchbase -  HTTP Access** dashboard provides insights into HTTP Rest API
 Use this dashboard to:
 * To understand user behavior accessing clusters and servers through Rest API.
 
-<img src={useBaseUrl('img/integrations/databases/Couchbase-HTTP-Access.png')} alt="Cassandra dashboards" />
+<img src={useBaseUrl('img/integrations/databases/Couchbase-HTTP-Access.png')} alt="Couchbase dashboards" />
 
 ## Create monitors for Couchbase app
 
+Sumo Logic provides pre-configured alerts available through [Sumo Logic monitors](/docs/alerts/monitors) to help you proactively determine if an Couchbase cluster is available and performing as expected. These monitors are based on metric and log data and include pre-set thresholds that reflect industry best practices and recommendations. For more information about individual alerts, refer to the [Couchbase Alerts](/docs/integrations/databases/couchbase#couchbase-alerts).
+
 import CreateMonitors from '../../reuse/apps/create-monitors.md';
 
 <CreateMonitors/>
 
+:::note
+- Ensure that you have [Manage Monitors role capability](/docs/manage/users-roles/roles/role-capabilities/#alerting) permissions to install the Couchbase Alerts.
+- You can only enable the set number of alerts. For more information, refer to [Monitors](/docs/alerts/monitors/create-monitor).
+:::
+
 ### Couchbase alerts
 
 <table>

docs/integrations/databases/mariadb.md

@@ -22,17 +22,17 @@ This app is tested with the following MariaDB versions:
 
 Configuring log and metric collection for the MariaDB app includes the following tasks.
 
-### Step 1: Fields in Sumo Logic
+### Step 1: Configure fields in Sumo Logic
 
-Following fields will always be created automatically as a part of app installation process:
+As part of the app installation process, the following fields will created by default:
 * `component`
 * `environment`
 * `db_system`
 * `db_cluster`
 * `db_cluster_address`
 * `db_cluster_port`
 
-If you're using MariaDB in a Kubernetes environment, these additional fields will get created automatically as a part of app installation process:
+Additionally, if you are using MariaDB in the Kubernetes environment, these following additional fields will be created by default as a part of the app installation process:
 * `pod_labels_component`
 * `pod_labels_environment`
 * `pod_labels_db_system`
@@ -41,7 +41,7 @@ If you're using MariaDB in a Kubernetes environment, these additional fields wil
 * `pod_labels_db_cluster_port`
 
 
-For information on setting up fields, see [Sumo Logic Fields](/docs/manage/fields).
+To learn more about setting up fields, refer to [Sumo Logic Fields](/docs/manage/fields).
 
 ### Step 2: Configure Collection
 
@@ -183,9 +183,11 @@ This section explains the steps to collect MariaDB logs from a Kubernetes enviro
     ```
    5. Sumo Logic Kubernetes collection will automatically start collecting logs from the pods having the annotations defined above.
    6. Verify logs in Sumo Logic.
-3. **FER to normalize the fields in Kubernetes environments.** Labels created in Kubernetes environments automatically are prefixed with pod_labels. To normalize these for our app to work, we will have Field Extraction Rule automatically created for Database Application Components named as **AppObservabilityMariaDBDatabaseFER**.
 
 
+<br/>**FER to normalize the fields in Kubernetes environments.** Labels created in Kubernetes environments automatically are prefixed with pod_labels. To normalize these for our app to work, we will have Field Extraction Rule automatically created for Database Application Components named as **AppObservabilityMariaDBDatabaseFER**.
+<br/>
+
 </TabItem>
 <TabItem value="non-k8s">
 
@@ -526,10 +528,17 @@ Use this dashboard to:
 
 ## Create monitors for MariaDB app
 
+Sumo Logic provides pre-configured alerts available through [Sumo Logic monitors](/docs/alerts/monitors) to help you proactively determine if an MariaDB cluster is available and performing as expected. These monitors are based on metric and log data and include pre-set thresholds that reflect industry best practices and recommendations. For more information about individual alerts, refer to the [MariaDB Alerts](/docs/integrations/databases/mariadb#mariadb-alerts).
+
 import CreateMonitors from '../../reuse/apps/create-monitors.md';
 
 <CreateMonitors/>
 
+:::note
+- Ensure that you have [Manage Monitors role capability](/docs/manage/users-roles/roles/role-capabilities/#alerting) permissions to install the MariaDB Alerts.
+- You can only enable the set number of alerts. For more information, refer to [Monitors](/docs/alerts/monitors/create-monitor).
+:::
+
 ### MariaDB alerts
 
 | Alert Type (Metrics/Logs) | Alert Name                                           | Alert Description                                                                                                                                        | Trigger Type (Critical / Warning) | Alert Condition | Recover Condition |

docs/integrations/databases/memcached.md

@@ -52,22 +52,22 @@ Jun 23 07:35:01 node03 memcached: \
 
 Configuring log and metric collection for the Memcached app includes the following tasks.
 
-### Step 1: Fields in Sumo Logic
+### Step 1: Configure fields in Sumo Logic
 
-Following fields will always be created automatically as a part of app installation process:
+As part of the app installation process, the following fields will created by default:
 * `component`
 * `environment`
 * `db_system`
 * `db_cluster`
 * `pod`
 
-If you're using Memcached in a Kubernetes environment, these additional fields will get created automatically as a part of app installation process:
+Additionally, if you are using Memcached in the Kubernetes environment, these following additional fields will be created by default as a part of the app installation process:
 * `pod_labels_component`
 * `pod_labels_environment`
 * `pod_labels_db_system`
 * `pod_labels_db_cluster`
 
-For information on setting up fields, see [Sumo Logic Fields](/docs/manage/fields).
+To learn more about setting up fields, refer to [Sumo Logic Fields](/docs/manage/fields).
 
 ### Step 2: Configure Logs and Metrics Collection for Memcached
 
@@ -199,8 +199,9 @@ This section explains the steps to collect Memcached logs from a Kubernetes envi
     kubectl describe pod <Memcached_pod_name>
     ```
    4. Sumo Logic Kubernetes collection will automatically start collecting logs from the pods having the annotations defined above.
-3. **FER to normalize the fields in Kubernetes environments.** Labels created in Kubernetes environments automatically are prefixed with pod_labels. To normalize these for our app to work, we will have Field Extraction Rule automatically created for Database Application Components named as **AppObservabilityMemcachedDatabaseFER**.
 
+<br/> **FER to normalize the fields in Kubernetes environments.** Labels created in Kubernetes environments automatically are prefixed with pod_labels. To normalize these for our app to work, we will have Field Extraction Rule automatically created for Database Application Components named as **AppObservabilityMemcachedDatabaseFER**.
+<br/>
 </TabItem>
 <TabItem value="non-k8s">
 
@@ -361,10 +362,17 @@ The **Memcached - Logs** dashboard helps you quickly analyze your Memcached erro
 
 ## Create monitors for Memcached app
 
+Sumo Logic provides pre-configured alerts available through [Sumo Logic monitors](/docs/alerts/monitors) to help you proactively determine if an Memcached cluster is available and performing as expected. These monitors are based on metric and log data and include pre-set thresholds that reflect industry best practices and recommendations. For more information about individual alerts, refer to the [Memcached Alerts](/docs/integrations/databases/memcached#memcached-alerts).
+
 import CreateMonitors from '../../reuse/apps/create-monitors.md';
 
 <CreateMonitors/>
 
+:::note
+- Ensure that you have [Manage Monitors role capability](/docs/manage/users-roles/roles/role-capabilities/#alerting) permissions to install the Memcached Alerts.
+- You can only enable the set number of alerts. For more information, refer to [Monitors](/docs/alerts/monitors/create-monitor).
+:::
+
 ### Memcached alerts
 <table>
   <tr>

docs/integrations/databases/mongodb.md

@@ -71,22 +71,22 @@ environment=* db_cluster=* db_system=mongodb  | json "log" as _rawlog nodrop
 
 This section provides instructions for configuring log and metric collection for the Sumo Logic app for MongoDB.
 
-### Step 1: Fields in Sumo Logic
+### Step 1: Configure fields in Sumo Logic
 
-Following fields will always be created automatically as a part of app installation process:
+As part of the app installation process, the following fields will created by default:
 * `component`
 * `environment`
 * `db_system`
 * `db_cluster`
 
-If you're using MongoDB in a Kubernetes environment, these additional fields will get created automatically as a part of app installation process:
+Additionally, if you are using Redis in the Kubernetes environment, these following additional fields will be created by default as a part of the app installation process:
 * `pod_labels_component`
 * `pod_labels_environment`
 * `pod_labels_db_system`
 * `pod_labels_db_cluster`
 
 
-For information on setting up fields, see [Sumo Logic Fields](/docs/manage/fields).
+To learn more about setting up fields, refer to [Sumo Logic Fields](/docs/manage/fields).
 
 
 ### Step 2: Configure Collection for MongoDB
@@ -218,7 +218,8 @@ Pivoting to Tracing data from Entity Inspector is possible only for “MongoDB a
      ```
    5. Sumo Logic Kubernetes collection will automatically start collecting logs from the pods having the annotations defined above.
 
-   3. **FER to normalize the fields in Kubernetes environments.** Labels created in Kubernetes environments automatically are prefixed with pod_labels. To normalize these for our app to work, we will have Field Extraction Rule automatically created for Database Application Components named as **AppObservabilityMongoDBDatabaseFER**.
+<br/>**FER to normalize the fields in Kubernetes environments.** Labels created in Kubernetes environments automatically are prefixed with pod_labels. To normalize these for our app to work, we will have Field Extraction Rule automatically created for Database Application Components named as **AppObservabilityMongoDBDatabaseFER**.
+<br/>
 
 </TabItem>
 <TabItem value="non-k8s">
@@ -460,10 +461,17 @@ Use this dashboard to:
 
 ## Create monitors for MongoDB app
 
+Sumo Logic provides pre-configured alerts available through [Sumo Logic monitors](/docs/alerts/monitors) to help you proactively determine if an MongoDB cluster is available and performing as expected. These monitors are based on metric and log data and include pre-set thresholds that reflect industry best practices and recommendations. For more information about individual alerts, refer to the [MongoDB Alerts](/docs/integrations/databases/mongodb#mongodb-alerts).
+
 import CreateMonitors from '../../reuse/apps/create-monitors.md';
 
 <CreateMonitors/>
 
+:::note
+- Ensure that you have [Manage Monitors role capability](/docs/manage/users-roles/roles/role-capabilities/#alerting) permissions to install the Couchbase Alerts.
+- You can only enable the set number of alerts. For more information, refer to [Monitors](/docs/alerts/monitors/create-monitor).
+:::
+
 ### MongoDB alerts
 
 | Name                                         | Description                                                                                                                                               | Trigger Type | Alert Conditions | Recover Conditions |