You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
@@ -41,16 +41,16 @@ To view your Managed Database's metrics and logs, use the Grafana dashboard whic
41
41
42
42
1. Create a Grafana user and retrieve their username and password by [following this procedure](/cockpit/how-to/retrieve-grafana-credentials/).
43
43
44
-
2. From the Scaleway console [Cockpit overview page](https://console.scaleway.com/cockpit/overview), click Open dashboards in the top right corner.
44
+
2. From the Scaleway console [Cockpit overview page](https://console.scaleway.com/cockpit/overview), click **Open dashboards** in the top right corner.
45
45
46
46
3. Enter your Grafana username and password to log in.
47
47
48
48
You are directed to the Scaleway Cockpit dashboards homepage.
49
49
50
50
## How to view and understand your Managed Database metrics
51
51
52
-
1. Click Open dashboards on the top right from the Scaleway Cockpit dashboards homepage.
53
-
2. Click Dashboards in the left menu, then Redis Overview in the list of products.
52
+
1. Click **Open dashboards** on the top right from the Scaleway Cockpit dashboards homepage.
53
+
2. Click **Dashboards** in the left menu, then **Redis Overview** in the list of products.
54
54
55
55
You are directed to the RDB Overview dashboard.
56
56
@@ -60,7 +60,7 @@ Metrics are refreshed every minute, and report on the following data:
60
60
61
61
- CPU usage
62
62
- Node usage
63
-
- Database Memory usage
63
+
- Database memory usage
64
64
- Network I/O
65
65
- Connected/Blocked clients
66
66
- Hits/Misses per second
@@ -79,7 +79,7 @@ At the top of the dashboard, you can configure the following parameters, that co
79
79
80
80
The log section is displayed below the metrics section.
81
81
82
-
Click Logs to collapse the tab and view your logs.
82
+
Click **Logs** to collapse the tab and view your logs.
83
83
84
84
You can [configure Redis™ advanced settings](/managed-databases-for-redis/how-to/configure-advanced-settings-redis) to define parameters for slow logs.
Copy file name to clipboardExpand all lines: pages/managed-databases-for-redis/troubleshooting/database-instance-connectivity-issues.mdx
+1-1Lines changed: 1 addition & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -60,7 +60,7 @@ You can carry out the following actions:
60
60
2.[Use Cockpit](/managed-databases-for-redis/how-to/monitor-redis-databases-cockpit) to check database logs and look for any activity or behavior that could explain the issue.
61
61
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:
62
62
63
-
- The resource ID of resource from which the connection was attempted
63
+
- The ID of the resource from which the connection was attempted
64
64
- 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.
Copy file name to clipboardExpand all lines: pages/managed-databases-for-redis/troubleshooting/database-instance-performance-issues.mdx
+1-1Lines changed: 1 addition & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -26,6 +26,6 @@ My Database Instance is not performing as expected.
26
26
27
27
## Solution
28
28
29
-
You can [Monitor usage metrics on Cockpit](/managed-databases-for-redis/how-to/monitor-redis-databases-cockpit) to check if the usage is nominal.
29
+
You can [monitor usage metrics on Cockpit](/managed-databases-for-redis/how-to/monitor-redis-databases-cockpit) to check if the usage is nominal.
30
30
31
31
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.
0 commit comments