edit-icon download-icon

About Redis console

Last Updated: Dec 25, 2017

The Redis console is a web application that manages ApsaraDB for Redis instances. On the console, you can create and manage instances, set networks and passwords, and perform other operations on the user interface.

Prerequisites

You log on to the Redis console by using your Alibaba Cloud account. If you do not have an Alibaba Cloud account, click register.

Console overview

Console homepage

The console homepage displays the same information for ApsaraDB for Redis instances of all types.

Log on to the Redis console, and go to the Instance List page, as shown in the following figure. (The figure here is only used for an example. See the actual interface when using this document.)

Instance List

On the Instance List page, the following information is displayed: Instance ID, Status, Memory Quota and Amount Used, Zone, Creation Time, Billing Method, and Network Type.

Note: Memory Quota and Amount Used is offline statistics made by the underlying system based on the collected information. A delay of about 10 minutes always exists.

Maintenance window

You can modify the O&M period on the Instance Information page. Alibaba Cloud maintains the instances during the O&M time, which may result in system flash. We recommend that you set the maintenance window in the idle service hours.

Maintenance Window

Performance monitoring

Click Instance ID to go to the Instance Information page. In the left-side navigation pane, choose Performance Monitoring to view historical performances of your ApsaraDB for Redis instances. Different metrics are displayed.

Performance Monitoring

Different metrics are displayed after you click Performance Monitoring. Metrics of basic monitoring groups are described as follows.

Basic metrics Description
Keys Total number of keys of all backend ApsaraDB for Redis instances. Data on all backend nodes of a cluster instance is aggregated.
Expires Total number of keys for which an expiration time is set.
ExpiredKeys Number of expired keys.
The value is the sum of all expired keys, excluding the number of keys for which an expiration time is set but do not expire currently. Besides, it indicates the number of accumulated expired keys, instead of the number of expired keys in the current time.
Note: In case of master-slave switchover, the value indicates the number of expired keys in the new master database.
EvictedKeys Number of evicted keys.
The value indicates the sum of keys which are evicted because the memory is used out, instead of the number of keys evicted in the current second.
Note: In case of master-slave switchover, the value indicates the number of expired keys in the new master database.
UsedMemory Memory in use currently.
When a new instance is created, database metadata is generated. For master-slave instances, the generated database metadata occupies a space of at least 30 MB. For cluster instances, the generated database metadata occupies a space of about 30 MB multiplied by the number of nodes. A space of at least 200 MB is occupied.
InFlow Current traffic per second at the backend ApsaraDB for Redis ingress. The unit is KB/s.
OutFlow Current traffic per second at the backend ApsaraDB for Redis egress. The unit is KB/s.
ConnCount Count of current client connections of ApsaraDB for Redis.
FailedCount It makes no sense for master-slave instances because the client is directly connected to the backend database. For cluster instances, the parameter indicates the number of failed operations from Proxy to ApsaraDB for Redis, including the number of abnormal operations caused by time-out, disconnection, or other exceptions.
For some ApsaraDB for Redis of earlier versions, the value is a historical value. In such case, no error is reported when FaileCount is not set. For ApsaraDB for Redis of the new version, the value indicates the statistical value in each second. In the future, the value indicates the statistical value in each second for ApsaraDB for Redis of later versions.
TotalQps QPS of ApsaraDB for Redis.
CpuUsage CPU usage of the current ApsaraDB for Redis backend.

Note: You can click Customize Metrics to monitor the number of accesses to different operating commands, for example, the number of accesses to the set command per second. For more information, see Performance Monitoring.

Alarm settings

Click Alarm Settings in the left-side navigation pane, and click the Alarm Settings button to go to the setting page of CloudMonitor.

Alarm settings

You can create a metric for ApsaraDB for Redis instances as guided. We recommend that you set a memory metric for all cluster instances to monitor the memory of sub-nodes of the cluster instances.

System parameters

You can set common parameters of ApsaraDB for Redis on the System Parameters page, for example, setting an eviction policy and notify-keypsace-events. For more information, see Parameter settings.

Backup and recovery

On the backup and recovery page, you can set a backup and the automatic backup time, and clone an instance. For more information, see Backup and recovery.

Thank you! We've received your feedback.