feat(red): fixes

Author: ldecarvalho-doc

pages/managed-databases-for-postgresql-and-mysql/troubleshooting/database-instance-connectivity-issues.mdx

@@ -5,7 +5,7 @@ meta:
 content:
   h1: Dealing with Database Instance connectivity issues
   paragraph: Troubleshoot Database Instance connectivity issues for Managed Databases for MySQL and PostgreSQL.
-tags: disk-full databases
+tags: connectivity databases
 dates:
   validation: 2025-01-29
   posted: 2025-01-29
@@ -145,5 +145,5 @@ Run the script in a terminal:
 ```
 export INSTANCE_IP=<xxx.xxx.xxx.xxx>
 export INSTANCE_PORT=<xxxxx>
-./troubleshoot.sh
+./rdb_troubleshoot.sh
 ```

pages/managed-databases-for-postgresql-and-mysql/troubleshooting/database-instance-performance-issues.mdx

@@ -5,7 +5,7 @@ meta:
 content:
   h1: Dealing with Database Instance performance issues
   paragraph: Troubleshoot Database Instance performance issues in Managed Databases for MySQL and PostgreSQL.
-tags: disk-full databases
+tags: databases performance
 dates:
   validation: 2025-01-29
   posted: 2025-01-29

pages/managed-databases-for-redis/troubleshooting/database-instance-connectivity-issues.mdx

@@ -33,7 +33,7 @@ You can check the following points to identify and act on what might be causing
 
 1. If TLS is enabled on the Database Instance, make sure the certificate is up to date, and that your client application is properly configured.
 2. Make sure your [ACLs](/managed-databases-for-redis/concepts/#allowed-ips) are [properly configured](/managed-databases-for-redis/how-to/manage-allowed-ip-addresses-redis).
-3. Make sure your Database Instance has not reached the maximum number of connections stipulated in the advanced settings of the Database Instance. You can monitor the number of connections on [Cockpit](/managed-databases-for-postgresql-and-mysql/how-to/monitor-databases-cockpit). You can also [adjust the advanced settings](/managed-databases-for-redis/how-to/configure-advanced-settings-redis) to accept a higher number of connections.
+3. Make sure your Database Instance has not reached the maximum number of connections stipulated in the advanced settings of the Database Instance. You can monitor the number of connections on Cockpit. You can also [adjust the advanced settings](/managed-databases-for-redis/how-to/configure-advanced-settings-redis) to accept a higher number of connections.
 4. [Monitor other usage metrics on Cockpit](/managed-databases-for-postgresql-and-mysql/how-to/monitor-databases-cockpit) to:
 
     - Check if the memory usage is nominal. High memory usage could trigger OOM Kills and cause disconnection
@@ -57,15 +57,15 @@ I cannot connect to my Database Instance through a Private Network.
 You can carry out the following actions:
 
 1. Try to connect to the Database Instance from the public endpoint, if one is available, to identify the possible origin (network or instance). This information can help you or the support team to identify the issue.
-2. [Use Cockpit](/managed-databases-for-postgresql-and-mysql/how-to/monitor-databases-cockpit) to check database logs and look for any activity or behavior that could explain the issue.
+2. [Use Cockpit](/managed-databases-for-redis/how-to/monitor-databases-cockpit) to check database logs and look for any activity or behavior that could explain the issue.
 3. Create a support ticket if the first two steps do not help troubleshoot the issue. In the body of the ticket, make sure you provide:
 
     - The resource ID of resource from which the connection was attempted
-    - The output of the `rdb_troubleshoot.sh` script, indicated below. Make sure you execute the script on the machine from which the connection was attempted.
+    - The output of the `redis_troubleshoot.sh` script, indicated below. Make sure you execute the script on the machine from which the connection was attempted.
 
 #### Database Instance connectivity check script
 
-`rdb_troubleshoot.sh`:
+`redis_troubleshoot.sh`:
 
 ```sh
 #!/bin/bash
@@ -89,7 +89,7 @@ function header() {
     echo -e "---------------------------------\n"
 }
 
-echo -e "\nRDB troubleshooting script\nThis script will run for several minutes to get enough information."
+echo -e "\nREDIS troubleshooting script\nThis script will run for several minutes to get enough information."
 header "Host information"
 if ! [ -x "$(command -v uname)" ]; then
   echo 'Skipped: uname command is not availabe.'
@@ -145,5 +145,5 @@ Run the script in a terminal:
 ```
 export INSTANCE_IP=<xxx.xxx.xxx.xxx>
 export INSTANCE_PORT=<xxxxx>
-./troubleshoot.sh
+./redis_troubleshoot.sh
 ```

pages/managed-databases-for-redis/troubleshooting/database-instance-performance-issues.mdx

@@ -0,0 +1,31 @@
+---
+meta:
+  title: Dealing with Database Instance performance issues
+  description: Troubleshoot Database Instance performance issues in Managed Databases for Redis™.
+content:
+  h1: Dealing with Database Instance performance issues
+  paragraph: Troubleshoot Database Instance performance issues in Managed Databases for Redis™.
+tags: databases performance
+dates:
+  validation: 2025-02-13
+  posted: 2025-02-13
+categories:
+  - managed-databases
+  - redis
+---
+
+## Problem
+
+My Database Instance is not performing as expected.
+
+## Possible causes
+
+- High data loads
+- High incoming traffic from specific apps or websites
+- Huge or sub-optimized SQL queries
+
+## Solution
+
+You can [Monitor usage metrics on Cockpit](/managed-databases-for-redis/how-to/monitor-databases-cockpit) to check if the usage is nominal.
+
+The Database Instance can be impacted by high data loads or unexpected high traffic from an app or website, for example. You can [scale up your Instance](/managed-databases-for-redis/how-to/scale-up-a-database-for-redis) if necessary.

pages/managed-databases-for-redis/troubleshooting/database-instance-unavailable.mdx

@@ -0,0 +1,33 @@
+---
+meta:
+  title: Dealing with Database Instance unavailability
+  description: Troubleshoot Database Instance unavailability for Managed Databases for Redis™.
+content:
+  h1: Dealing with Database Instance unavailability
+  paragraph: Troubleshoot Database Instance unavailability for Managed Databases for Redis™L.
+tags: unavailability databases
+dates:
+  validation: 2025-02-17
+  posted: 2025-02-17
+categories:
+  - managed-databases
+  - redis
+---
+
+## Problem
+
+My Database Instance is unavailable.
+
+## Possible causes
+
+- High data loads
+- High incoming traffic from specific apps or websites
+
+## Solution
+
+You can monitor your Database Instance activity to be able to quickly identify and act on irregular activities that might be causing the instability/unavailability.
+
+[Monitor usage metrics on Cockpit](/managed-databases-for-redis/how-to/monitor-databases-cockpit) to:
+
+    - Check if the usage is regular. Database Instance can be impacted by high data loads or unexpected high traffic from an app or website, for example
+    - Check the Database Instance logs for any unusual or suspicious activity