Note
Refer to the How to activate pre-configured alerts to learn how to do so.
How to monitor your Redis™ Database Instance with Scaleway Cockpit
Reviewed on 05 June 2025 • Published on 05 June 2025
You can view your Managed Database for Redis™ metrics and logs using Scaleway Cockpit. Managed Databases are fully integrated into Cockpit.
Monitoring is available for:
- Primary Database Instance nodes
- Secondary nodes (if in High Availability or in Cluster mode)
This page explains how to get started with Scaleway Cockpit for viewing your Managed Database for Redis™’ metrics and logs.
Before you startLink to this anchor
To complete the actions presented below, you must have:
- A Scaleway account logged into the console
- Owner status or IAM permissions allowing you to perform actions in the intended Organization
- A Redis™ Database Instance
How to activate your CockpitLink to this anchor
Scaleway Cockpit is activated by default if you have created any Scaleway resources integrated with Cockpit.
How to access the Grafana dashboardLink to this anchor
To view your Managed Database’s metrics and logs, use the Grafana dashboard which is accessible from the Scaleway console:
- First, you must create a user and their associated credentials (a username and password) for Grafana
- Then, you can use these credentials to access the Grafana dashboard for all your Scaleway products, via the Scaleway console.
-
Create a Grafana user and retrieve their username and password by following this procedure.
-
From the Scaleway console Cockpit overview page, click Open dashboards in the top right corner.
-
Enter your Grafana username and password to log in.
You are directed to the Scaleway Cockpit dashboards homepage.
How to view and understand your Managed Database metricsLink to this anchor
-
Click Open dashboards on the top right from the Scaleway Cockpit dashboards homepage.
-
Click Dashboards in the left menu, then Redis Overview in the list of products.
You are directed to the RDB Overview dashboard.
Metrics are refreshed every minute, and report on the following data:
- CPU usage
- Node usage
- Database memory usage
- Network I/O
- Connected/Blocked clients
- Hits/Misses per second
- Expiring/Not-expiring keys
- Expired/Evicted keys
Choosing metric parametersLink to this anchor
At the top of the dashboard, you can configure the following parameters, that control which metrics are displayed:
- Resource name - Select a specific Database Instance to monitor.
- Node - Choose a specific node (main or replica). In a High Availability (HA) cluster, both nodes might switch from main to replica and vice versa. You might see two versions of the same node, as main and as replica. If you select main for a specific node, you will only see the node’s activity when it was the main, and vice-versa. In Cluster mode, all nodes are considered primary and each have a data subset.
- Timeframe - Get metrics from the last five minutes up to 31 days (free plan) and 365 days (premium plan).
Viewing logsLink to this anchor
The log section is displayed below the metrics section.
Click Logs to collapse the tab and view your logs.
You can configure Redis™ advanced settings to define parameters for slow logs.
| Parameter | Description |
|---|---|
slowlog-log-slower-than | Specifies how many microseconds (1 second = 1,000,000 microseconds) the execution time of a command must exceed to be recorded in the slow query log. |
slowlog-max-len | Specifies the maximum number of slow query logs that the server retains. The server retains multiple slow query logs on a first-in-first-out (FIFO) basis. When the number of slow query logs stored by the server equals the slowlog-max-len value, the server will delete the oldest slow query log before adding a new one. |
How to activate pre-configured alertsLink to this anchor
You can activate Scaleway pre-configured alerts for your Managed Databases with Scaleway Cockpit.
By default, two pre-configured alerts are available for Managed Databases:
HighCpuUsage- Alerts if CPU usage has been higher than 80% for 10 consecutive minutesHighMemoryUsage- RAM usage has been higher than 80% for 10 consecutive minutes
You can also configure your own alerts and set values for each of the parameters below to define when you want to be alerted:
| Alert | Description |
|---|---|
rkv_cluster_node_cpu_seconds_total | Total amount of CPU time consumed by the Database Instance, measured in seconds |
rkv_cluster_node_memory_MemAvailable_bytes | Amount of memory available |
rkv_cluster_node_memory_MemTotal_bytes | Total installed physical memory (RAM) |
rkv_cluster_redis_blocked_clients | Total blocked connections on Redis™ |
rkv_cluster_redis_config_maxclients | Maximum number of connections configured |
rkv_cluster_redis_connected_clients | Total active connections on Redis™ |
rkv_cluster_redis_db_keys | Total number of keys stored |
rkv_cluster_redis_db_keys_expiring | Total number of keys that have an expiration date |
rkv_cluster_redis_evicted_keys_total | Total number of keys that were evicted because of memory pressure |
rkv_cluster_redis_expired_keys_total | Total number of keys that have expired |
rkv_cluster_redis_keyspace_hits_total | Total number of requests that found a match in the database |
rkv_cluster_redis_keyspace_misses_total | Total number of request that did not find a match in the database |
rkv_cluster_redis_memory_max_bytes | Amount of memory available for Redis™ |
rkv_cluster_redis_memory_used_bytes | Amount of memory used by Redis™ |
rkv_cluster_redis_net_input_bytes_total | Total incoming traffic received by Redis™ from clients, measured in bytes |
rkv_cluster_redis_net_output_bytes_total | Total outgoing traffic sent by Redis™, measured in bytes |
Was this page helpful?