diff --git a/umn/source/_static/images/en-us_image_0000001505063901.png b/umn/source/_static/images/en-us_image_0000001505063901.png new file mode 100644 index 0000000..0eed9cc Binary files /dev/null and b/umn/source/_static/images/en-us_image_0000001505063901.png differ diff --git a/umn/source/_static/images/en-us_image_0266235369.png b/umn/source/_static/images/en-us_image_0266235369.png new file mode 100644 index 0000000..240e1d2 Binary files /dev/null and b/umn/source/_static/images/en-us_image_0266235369.png differ diff --git a/umn/source/_static/images/en-us_image_0266235377.png b/umn/source/_static/images/en-us_image_0266235377.png new file mode 100644 index 0000000..fc28388 Binary files /dev/null and b/umn/source/_static/images/en-us_image_0266235377.png differ diff --git a/umn/source/_static/images/en-us_image_0266235408.png b/umn/source/_static/images/en-us_image_0266235408.png new file mode 100644 index 0000000..240e1d2 Binary files /dev/null and b/umn/source/_static/images/en-us_image_0266235408.png differ diff --git a/umn/source/_static/images/en-us_image_0266235415.png b/umn/source/_static/images/en-us_image_0266235415.png new file mode 100644 index 0000000..fc28388 Binary files /dev/null and b/umn/source/_static/images/en-us_image_0266235415.png differ diff --git a/umn/source/_static/images/en-us_image_0266235461.jpg b/umn/source/_static/images/en-us_image_0266235461.jpg deleted file mode 100644 index 76e70fb..0000000 Binary files a/umn/source/_static/images/en-us_image_0266235461.jpg and /dev/null differ diff --git a/umn/source/_static/images/en-us_image_0266235565.jpg b/umn/source/_static/images/en-us_image_0266235565.jpg deleted file mode 100644 index 30be576..0000000 Binary files a/umn/source/_static/images/en-us_image_0266235565.jpg and /dev/null differ diff --git a/umn/source/change_history.rst b/umn/source/change_history.rst index 8ef4ae6..62234e6 100644 --- a/umn/source/change_history.rst +++ b/umn/source/change_history.rst @@ -8,6 +8,11 @@ Change History +-----------------------------------+---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+ | Released On | What's New | +===================================+===================================================================================================================================================================================================================================================================================================================================================================================================================================================================================================+ +| 2023-01-31 | Modified the following content: | +| | | +| | - Added description about Redis 6.0, such as :ref:`Redis 6.0 Instance Specifications `. | +| | - Added :ref:`Configuring SSL `. | ++-----------------------------------+---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+ | 2022-10-19 | Added the following FAQs: | | | | | | :ref:`Why Does a Key Disappear in Redis? ` | @@ -24,7 +29,7 @@ Change History +-----------------------------------+---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+ | 2022-08-29 | Modified the following content: | | | | -| | Added description about security groups and whitelist configuration in sections :ref:`Creating a DCS Redis Instance `, :ref:`Security Group Configurations `, :ref:`What Should I Do If an Error Is Returned When I Use the Jedis Connection Pool? `, :ref:`How Do I Troubleshoot Redis Connection Failures? `, and :ref:`Why Aren't Security Groups Configured for DCS Redis 4.0 and 5.0 Instances? ` | +| | Added description about security groups and whitelist configuration in sections :ref:`Creating a DCS Redis Instance `, :ref:`Security Group Configurations `, :ref:`What Should I Do If an Error Is Returned When I Use the Jedis Connection Pool? `, :ref:`How Do I Troubleshoot Redis Connection Failures? `, and :ref:`Why Aren't Security Groups Configured for DCS Redis 4.0/5.0/6.0 Instances? ` | +-----------------------------------+---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+ | 2022-08-09 | Modified the following content: | | | | @@ -49,7 +54,7 @@ Change History | | - Updated the commands supported and disabled by Web CLI in section :ref:`Web CLI Commands `. | | | - Added the following FAQs: | | | | -| | - :ref:`Why Aren't Security Groups Configured for DCS Redis 4.0 and 5.0 Instances? ` | +| | - :ref:`Why Aren't Security Groups Configured for DCS Redis 4.0/5.0/6.0 Instances? ` | | | - :ref:`Can I Obtain the Addresses of the Nodes in a Cluster DCS Redis Instance? ` | | | - :ref:`Does DCS for Redis Provide Backend Management Software? ` | | | - :ref:`Why Is "Error in execution" Returned When I Access Redis? ` | @@ -89,7 +94,7 @@ Change History | | - Modified description about the process for creating instances and added description about creating DCS Redis 4.0 and 5.0 instances in section :ref:`Creating a DCS Redis Instance `. | | | - Added the description about the sold-out tip for the AZ parameter in section :ref:`Creating a DCS Redis Instance `. | | | - Modified descriptions in sections :ref:`Accessing a DCS Redis Instance Through redis-cli ` and :ref:`Jedis `. | -| | - Added section :ref:`Accessing a DCS Redis 4.0 or 5.0 Instance on the Console `. | +| | - Added section :ref:`Accessing a DCS Redis 4.0/5.0/6.0 Instance on the Console `. | | | - Added description about DCS Redis 4.0 and 5.0 instances in section :ref:`Viewing Details of a DCS Instance `. | | | - Optimized the classification of operations in chapter :ref:`Operation Guide `. | | | - Added notes on changing the DCS instance specifications in section :ref:`Modifying DCS Instance Specifications `. | diff --git a/umn/source/faqs/client_and_network_connection/how_do_i_troubleshoot_redis_connection_failures.rst b/umn/source/faqs/client_and_network_connection/how_do_i_troubleshoot_redis_connection_failures.rst index 685b9e2..6b73f0d 100644 --- a/umn/source/faqs/client_and_network_connection/how_do_i_troubleshoot_redis_connection_failures.rst +++ b/umn/source/faqs/client_and_network_connection/how_do_i_troubleshoot_redis_connection_failures.rst @@ -29,7 +29,7 @@ How Do I Troubleshoot Redis Connection Failures? For details, see :ref:`Security Group Configurations `. -- For a DCS Redis 4.0 or 5.0 instance, check the whitelist configuration. +- For a DCS Redis 4.0/5.0/6.0 instance, check the whitelist configuration. If the instance has a whitelist, ensure that the client IP address is included in the whitelist. Otherwise, the connection will fail. diff --git a/umn/source/faqs/client_and_network_connection/security_group_configurations.rst b/umn/source/faqs/client_and_network_connection/security_group_configurations.rst index cb8b24e..e5e948e 100644 --- a/umn/source/faqs/client_and_network_connection/security_group_configurations.rst +++ b/umn/source/faqs/client_and_network_connection/security_group_configurations.rst @@ -5,10 +5,10 @@ Security Group Configurations ============================= -DCS Redis 3.0/4.0/5.0 instances are deployed in different modes. Therefore, the access control method varies. +DCS helps you control access to your DCS instances in the following ways, depending on the deployment mode: - To control access to DCS Redis 3.0 instances, you can use security groups. Whitelists are not supported. Security group operations are described in this section. -- To control access to DCS Redis 4.0/5.0 instances, you can use whitelists. Security groups are not supported. Whitelist operations are described in :ref:`Managing IP Address Whitelist `. +- To control access to DCS Redis 4.0/5.0/6.0 instances, you can use whitelists. Security groups are not supported. Whitelist operations are described in :ref:`Managing IP Address Whitelist `. This section describes how to configure a security group for accessing a DCS instance **within a VPC**. diff --git a/umn/source/faqs/data_backup_export_and_migration/can_i_export_backup_data_of_dcs_redis_instances_to_rdb_files_using_the_console.rst b/umn/source/faqs/data_backup_export_and_migration/can_i_export_backup_data_of_dcs_redis_instances_to_rdb_files_using_the_console.rst index 3d49618..6ff23b9 100644 --- a/umn/source/faqs/data_backup_export_and_migration/can_i_export_backup_data_of_dcs_redis_instances_to_rdb_files_using_the_console.rst +++ b/umn/source/faqs/data_backup_export_and_migration/can_i_export_backup_data_of_dcs_redis_instances_to_rdb_files_using_the_console.rst @@ -11,6 +11,6 @@ Can I Export Backup Data of DCS Redis Instances to RDB Files Using the Console? **redis-cli -h {redis_address} -p 6379 [-a password] --rdb {output.rdb}** -- Redis 4.0 and 5.0 +- Redis 4.0/5.0 - Yes. Backup data of a DCS Redis 4.0 or 5.0 instance is exported from the console to RDB files. You cannot use redis-cli to export such data to RDB files. + Yes. DCS Redis 4.0/5.0/6.0 instances support AOF and RDB persistence. You can back up data to RDB and AOF files on the console and download the files. diff --git a/umn/source/faqs/instance_scaling_and_upgrade/are_services_interrupted_during_specification_modification.rst b/umn/source/faqs/instance_scaling_and_upgrade/are_services_interrupted_during_specification_modification.rst index d9f5bb7..47b9a19 100644 --- a/umn/source/faqs/instance_scaling_and_upgrade/are_services_interrupted_during_specification_modification.rst +++ b/umn/source/faqs/instance_scaling_and_upgrade/are_services_interrupted_during_specification_modification.rst @@ -7,32 +7,23 @@ Are Services Interrupted During Specification Modification? You are advised to change the instance specifications during off-peak hours because specification modification has the following impacts: -- **Impact of instance type changes:** - - - From single-node to master/standby for a DCS Redis 3.0 instance: - - The instance cannot be connected for several seconds and remains read-only for about 1 minute. - - - From master/standby to Proxy Cluster for a DCS Redis 3.0 instance: - - The instance cannot be connected and remains read-only for 5 to 30 minutes. - -- **Impact of capacity expansion and reduction:** +- **Impact of scaling:** - Single-node and master/standby - The DCS Redis 3.0, 4.0, or 5.0 instance cannot be connected for several seconds and remains read-only for about 1 minute. + - A DCS Redis 4.0/5.0/6.0 instance will be disconnected for several seconds and remain read-only for about 1 minute. + - A DCS Redis 3.0 instance will be disconnected and remain read-only for 5 to 30 minutes. + - For scaling up, only the memory of the instance is expanded. The CPU processing capability is not improved. + - Data of single-node instances may be lost because they do not support data persistence. After scaling, check whether the data is complete and import data if required. + - Backup records of master/standby instances cannot be used after scaling down. - For capacity expansion, only the memory of the instance is expanded. The CPU processing capability is not improved. + - Cluster - Data of single-node instances may not be retained because they do not support data persistence. After the scaling, check whether the data is complete and import data if required. - - - Proxy Cluster - - The instance can be connected, but the CPU will be occupied and the latency will increase during data migration. During capacity expansion, new Redis Server nodes are added, and data is automatically balanced to the new nodes. - - - Redis Cluster - - The instance can be connected, but the CPU usage and latency will increase during data migration. During capacity expansion, new Redis Server nodes are added, and data is automatically balanced to the new nodes. - - - Backup records created before the capacity change cannot be restored. + - If the shard quantity is not decreased, the instance can always be connected, but the CPU usage will increase, compromising performance by up to 20%, and the latency will increase during data migration. + - During scaling up, new Redis Server nodes are added, and data is automatically balanced to the new nodes. + - Nodes will be deleted if the shard quantity decreases. To prevent disconnection, ensure that the deleted nodes are not directly referenced in your application. + - Ensure that the used memory of each node is less than 70% of the maximum memory per node of the new flavor. Otherwise, you cannot perform the scale-in. + - If the memory becomes full during scaling due to a large amount of data being written, scaling will fail. Modify specifications during off-peak hours. + - Scaling involves data migration. The latency for accessing the key being migrated increases. For a Redis Cluster instance, ensure that the client can properly process the **MOVED** and **ASK** commands. Otherwise, requests will fail. + - Before scaling, perform cache analysis to ensure that no big keys (>= 512 MB) exist in the instance. Otherwise, scaling may fail. + - Backup records created before scaling cannot be restored. diff --git a/umn/source/faqs/instance_scaling_and_upgrade/can_dcs_redis_instances_be_upgraded_for_example_from_redis_3.0_to_redis_4.0_or_5.0.rst b/umn/source/faqs/instance_scaling_and_upgrade/can_dcs_redis_instances_be_upgraded_for_example_from_redis_4.0_to_5.0.rst similarity index 67% rename from umn/source/faqs/instance_scaling_and_upgrade/can_dcs_redis_instances_be_upgraded_for_example_from_redis_3.0_to_redis_4.0_or_5.0.rst rename to umn/source/faqs/instance_scaling_and_upgrade/can_dcs_redis_instances_be_upgraded_for_example_from_redis_4.0_to_5.0.rst index 2d2fff7..f1970f7 100644 --- a/umn/source/faqs/instance_scaling_and_upgrade/can_dcs_redis_instances_be_upgraded_for_example_from_redis_3.0_to_redis_4.0_or_5.0.rst +++ b/umn/source/faqs/instance_scaling_and_upgrade/can_dcs_redis_instances_be_upgraded_for_example_from_redis_4.0_to_5.0.rst @@ -2,9 +2,9 @@ .. _dcs-faq-0730043: -Can DCS Redis Instances Be Upgraded, for Example, from Redis 3.0 to Redis 4.0 or 5.0? -===================================================================================== +Can DCS Redis Instances Be Upgraded, for Example, from Redis 4.0 to 5.0? +======================================================================== -No. Different Redis versions use different underlying architectures. The Redis version used by a DCS instance cannot be changed once the instance is created. However, you will be informed of any defects or problems found in Redis. +No. Different Redis versions use different underlying architectures. The Redis version used by a DCS instance cannot be changed once the instance is created. For example, you cannot change a DCS Redis 4.0 instance to Redis 5.0. However, you will be informed of any defects or problems found in Redis. If your service requires the features of higher Redis versions, create a DCS Redis instance of a higher version and then migrate data from the original instance to the new one. For details on how to migrate data, see :ref:`Migrating Data with DCS `. diff --git a/umn/source/faqs/instance_scaling_and_upgrade/index.rst b/umn/source/faqs/instance_scaling_and_upgrade/index.rst index 1d75db8..3e70490 100644 --- a/umn/source/faqs/instance_scaling_and_upgrade/index.rst +++ b/umn/source/faqs/instance_scaling_and_upgrade/index.rst @@ -5,7 +5,7 @@ Instance Scaling and Upgrade ============================ -- :ref:`Can DCS Redis Instances Be Upgraded, for Example, from Redis 3.0 to Redis 4.0 or 5.0? ` +- :ref:`Can DCS Redis Instances Be Upgraded, for Example, from Redis 4.0 to 5.0? ` - :ref:`Are Services Interrupted If Maintenance is Performed During the Maintenance Time Window? ` - :ref:`Are Instance Resources Affected During Specification Modification? ` - :ref:`Are Services Interrupted During Specification Modification? ` @@ -15,7 +15,7 @@ Instance Scaling and Upgrade :maxdepth: 1 :hidden: - can_dcs_redis_instances_be_upgraded_for_example_from_redis_3.0_to_redis_4.0_or_5.0 + can_dcs_redis_instances_be_upgraded_for_example_from_redis_4.0_to_5.0 are_services_interrupted_if_maintenance_is_performed_during_the_maintenance_time_window are_instance_resources_affected_during_specification_modification are_services_interrupted_during_specification_modification diff --git a/umn/source/faqs/monitoring_and_alarm/why_is_the_rejected_connections_metric_displayed.rst b/umn/source/faqs/monitoring_and_alarm/why_is_the_rejected_connections_metric_displayed.rst index 8cd3088..7bfc1f6 100644 --- a/umn/source/faqs/monitoring_and_alarm/why_is_the_rejected_connections_metric_displayed.rst +++ b/umn/source/faqs/monitoring_and_alarm/why_is_the_rejected_connections_metric_displayed.rst @@ -5,4 +5,8 @@ Why Is the Rejected Connections Metric Displayed? ================================================= -If the **Rejected Connections** metric is displayed, check if the number of connected clients exceeds the maximum allowed number of connections of the instances. To check the maximum allowed number of connections, go to the **Parameters** tab page of the instance and check the value of the **maxclients** parameter. +If the **Rejected Connections** metric is displayed, check if the number of connected clients exceeds the maximum allowed number of connections of the instances. + +To check the maximum allowed number of connections, go to the **Parameters** tab page of the instance and check the value of the **maxclients** parameter. (Proxy Cluster instances do not have this parameter. You can view the maximum number of connections on the instance creation page.) + +To check the current number of connections, go to the **Performance Monitoring** tab page of the instance and check the **Connected Clients** metric. diff --git a/umn/source/faqs/redis_commands/how_do_i_clear_redis_data.rst b/umn/source/faqs/redis_commands/how_do_i_clear_redis_data.rst index d56c9cc..23aa521 100644 --- a/umn/source/faqs/redis_commands/how_do_i_clear_redis_data.rst +++ b/umn/source/faqs/redis_commands/how_do_i_clear_redis_data.rst @@ -15,14 +15,14 @@ How Do I Clear Redis Data? Run the **FLUSHDB** command to clear the data in the currently selected DB. -- Redis 4.0 and 5.0 +- Redis 4.0/5.0/6.0 - To clear data of a DCS Redis 4.0 or 5.0 instance, you can run the **FLUSHDB** or **FLUSHALL** command in redis-cli, use the data clearing function on the DCS console, or run the **FLUSHDB** command on Web CLI. + To clear data of a DCS Redis 4.0/5.0/6.0 instance, you can run the **FLUSHDB** or **FLUSHALL** command in redis-cli, use the data clearing function on the DCS console, or run the **FLUSHDB** command on Web CLI. To clear data of a Redis Cluster instance, run the **FLUSHDB** or **FLUSHALL** command on every shard of the instance. Otherwise, data may not be completely cleared. .. note:: - - Currently, only DCS Redis 4.0 and 5.0 instances support data clearing by using the DCS console and by running the **FLUSHDB** command on Web CLI. + - Currently, only DCS Redis 4.0 and later instances support data clearing by using the DCS console and by running the **FLUSHDB** command on Web CLI. - When you run the **FLUSHDB** command on Web CLI, only one shard is cleared at a time. If there are multiple shards, connect to and run the **FLUSHDB** command on each master node. - Redis Cluster data cannot be cleared by using Web CLI. diff --git a/umn/source/faqs/redis_usage/can_i_customize_or_change_the_port_for_accessing_a_dcs_instance.rst b/umn/source/faqs/redis_usage/can_i_customize_or_change_the_port_for_accessing_a_dcs_instance.rst index 24417d3..26f0b28 100644 --- a/umn/source/faqs/redis_usage/can_i_customize_or_change_the_port_for_accessing_a_dcs_instance.rst +++ b/umn/source/faqs/redis_usage/can_i_customize_or_change_the_port_for_accessing_a_dcs_instance.rst @@ -5,14 +5,14 @@ Can I Customize or Change the Port for Accessing a DCS Instance? ================================================================ -You cannot customize or change the port for accessing a DCS Redis 3.0 instance. You can customize and change the port for accessing a DCS Redis 4.0 or 5.0 instance. +You cannot customize or change the port for accessing a DCS Redis 3.0 instance. You can customize and change the port for accessing a DCS Redis 4.0 or later instance. - Redis 3.0 Use port 6379 for intra-VPC access. -- Redis 4.0 and Redis 5.0 +- Redis 4.0 and later - You can specify a port (ranging from 1 to 65535) or use the default port (6379) for accessing a DCS Redis 4.0 or 5.0 instance. If no port is specified, the default port will be used. + You can specify a port (ranging from 1 to 65535) or use the default port (6379) for accessing an instance. If no port is specified, the default port will be used. If the instance and the client use different security groups, you must configure access rules for the security groups, allowing access through the specified port. For details, see :ref:`Security Group Configurations `. diff --git a/umn/source/faqs/redis_usage/can_i_obtain_the_addresses_of_the_nodes_in_a_cluster_dcs_redis_instance.rst b/umn/source/faqs/redis_usage/can_i_obtain_the_addresses_of_the_nodes_in_a_cluster_dcs_redis_instance.rst index d56b11b..6eab308 100644 --- a/umn/source/faqs/redis_usage/can_i_obtain_the_addresses_of_the_nodes_in_a_cluster_dcs_redis_instance.rst +++ b/umn/source/faqs/redis_usage/can_i_obtain_the_addresses_of_the_nodes_in_a_cluster_dcs_redis_instance.rst @@ -7,7 +7,7 @@ Can I Obtain the Addresses of the Nodes in a Cluster DCS Redis Instance? Cluster DCS Redis 3.0 instances (Proxy Cluster type) are used in the same way that you use single-node or master/standby instances. You do not need to know the backend node addresses. -For a cluster DCS Redis 4.0 or 5.0 instance (Redis Cluster type), run the **CLUSTER NODES** command to obtain node addresses: +For a cluster DCS Redis 4.0/5.0/ instance (Redis Cluster type), run the **CLUSTER NODES** command to obtain node addresses: **redis-cli -h {redis_address} -p {redis_port} -a {redis_password} cluster nodes** diff --git a/umn/source/faqs/redis_usage/does_dcs_for_redis_support_sentinel.rst b/umn/source/faqs/redis_usage/does_dcs_for_redis_support_sentinel.rst index c248cb5..8c3abdc 100644 --- a/umn/source/faqs/redis_usage/does_dcs_for_redis_support_sentinel.rst +++ b/umn/source/faqs/redis_usage/does_dcs_for_redis_support_sentinel.rst @@ -5,6 +5,6 @@ Does DCS for Redis Support Sentinel? ==================================== -Yes. Redis Sentinel is supported by DCS for Redis 4.0 and 5.0 and is enabled by default. Sentinel constantly checks if master and replica nodes are running properly. If the master is not running properly, Sentinel starts a failover process and promotes a replica to master. +Cluster instances and master/standby DCS Redis 4.0/5.0/6.0 instances support Sentinels. Sentinels monitor the running status of both the master and standby nodes of a master/standby instance and each shard of a cluster instance. If the master node becomes faulty, a failover will be performed. However, DCS for Redis 3.0 does not support Redis Sentinel. Instead, it uses keepalive to monitor master and replica nodes and to manage failovers. diff --git a/umn/source/faqs/redis_usage/index.rst b/umn/source/faqs/redis_usage/index.rst index 06f04cb..c7e1ea1 100644 --- a/umn/source/faqs/redis_usage/index.rst +++ b/umn/source/faqs/redis_usage/index.rst @@ -7,7 +7,7 @@ Redis Usage - :ref:`Why Is CPU Usage of a DCS Redis Instance 100%? ` - :ref:`Can I Change the VPC and Subnet for a DCS Redis Instance? ` -- :ref:`Why Aren't Security Groups Configured for DCS Redis 4.0 and 5.0 Instances? ` +- :ref:`Why Aren't Security Groups Configured for DCS Redis 4.0/5.0/6.0 Instances? ` - :ref:`Do DCS Redis Instances Limit the Size of a Key or Value? ` - :ref:`Can I Obtain the Addresses of the Nodes in a Cluster DCS Redis Instance? ` - :ref:`Why Is Available Memory of a DCS Redis 3.0 Instance Smaller Than Instance Cache Size? ` @@ -35,7 +35,7 @@ Redis Usage why_is_cpu_usage_of_a_dcs_redis_instance_100pct can_i_change_the_vpc_and_subnet_for_a_dcs_redis_instance - why_arent_security_groups_configured_for_dcs_redis_4.0_and_5.0_instances + why_arent_security_groups_configured_for_dcs_redis_4.0_5.0_6.0_instances do_dcs_redis_instances_limit_the_size_of_a_key_or_value can_i_obtain_the_addresses_of_the_nodes_in_a_cluster_dcs_redis_instance why_is_available_memory_of_a_dcs_redis_3.0_instance_smaller_than_instance_cache_size diff --git a/umn/source/faqs/redis_usage/why_arent_security_groups_configured_for_dcs_redis_4.0_5.0_6.0_instances.rst b/umn/source/faqs/redis_usage/why_arent_security_groups_configured_for_dcs_redis_4.0_5.0_6.0_instances.rst new file mode 100644 index 0000000..7b9abf3 --- /dev/null +++ b/umn/source/faqs/redis_usage/why_arent_security_groups_configured_for_dcs_redis_4.0_5.0_6.0_instances.rst @@ -0,0 +1,12 @@ +:original_name: dcs-faq-0730014.html + +.. _dcs-faq-0730014: + +Why Aren't Security Groups Configured for DCS Redis 4.0/5.0/6.0 Instances? +========================================================================== + +Currently, DCS Redis 4.0/5.0/6.0 instances use VPC endpoints and do not support security groups. You can configure whitelists instead. For details, see :ref:`Managing IP Address Whitelist `. + +To allow access only from specific IP addresses to a DCS Redis instance, add the IP addresses to the instance whitelist. + +If no whitelists are added to the instance whitelist or the whitelist function is disabled, all IP addresses that can communicate with the VPC can access the instance. diff --git a/umn/source/faqs/redis_usage/why_arent_security_groups_configured_for_dcs_redis_4.0_and_5.0_instances.rst b/umn/source/faqs/redis_usage/why_arent_security_groups_configured_for_dcs_redis_4.0_and_5.0_instances.rst deleted file mode 100644 index 5b4a297..0000000 --- a/umn/source/faqs/redis_usage/why_arent_security_groups_configured_for_dcs_redis_4.0_and_5.0_instances.rst +++ /dev/null @@ -1,12 +0,0 @@ -:original_name: dcs-faq-0730014.html - -.. _dcs-faq-0730014: - -Why Aren't Security Groups Configured for DCS Redis 4.0 and 5.0 Instances? -========================================================================== - -Currently, DCS Redis 4.0 and Redis 5.0 instances use VPC endpoints and do not support security groups. You can configure whitelists instead. For details, see :ref:`Managing IP Address Whitelist `. - -To allow access only from specific IP addresses to a DCS Redis 4.0 or 5.0 instance, add the IP addresses to the instance whitelist. - -If no whitelists are added to the instance whitelist or the whitelist function is disabled, all IP addresses that can communicate with the VPC can access the instance. diff --git a/umn/source/getting_started/accessing_an_instance/access_in_different_languages/clients_in_python.rst b/umn/source/getting_started/accessing_an_instance/access_in_different_languages/clients_in_python.rst index 04c718f..08e3dd4 100644 --- a/umn/source/getting_started/accessing_an_instance/access_in_different_languages/clients_in_python.rst +++ b/umn/source/getting_started/accessing_an_instance/access_in_different_languages/clients_in_python.rst @@ -48,7 +48,7 @@ Procedure a. Install Python and redis-py. - #. If the system does not provide Python, run the following **yum** command to install it. + #. If the system does not provide Python, run the **yum** command to install it. #. Run the following command to download and decompress the redis-py package: @@ -116,15 +116,15 @@ Procedure #. Run the **python** command to enter the CLI mode. - #. Run the following command to access the chosen DCS Redis instance: + #. Run the following command to access the chosen DCS Redis instance. If the instance does not have a password, exclude **password='******'** from the command. .. code-block:: >>> from rediscluster import RedisCluster - >>> startup_nodes = [{"host": "192.168.0.143", "port": "6379"}] + >>> startup_nodes = [{"host": "192.168.0.143", "port": "6379"},{"host": "192.168.0.144", "port": "6379"},{"host": "192.168.0.145", "port": "6379"},{"host": "192.168.0.146", "port": "6379"}] - >>> rc = RedisCluster(startup_nodes=startup_nodes, decode_responses=True) + >>> rc = RedisCluster(startup_nodes=startup_nodes, decode_responses=True, password='******') >>> rc.set("foo", "bar") True diff --git a/umn/source/getting_started/accessing_an_instance/accessing_a_dcs_redis_4.0_or_5.0_instance_on_the_console.rst b/umn/source/getting_started/accessing_an_instance/accessing_a_dcs_redis_4.0_5.0_6.0_instance_on_the_console.rst similarity index 75% rename from umn/source/getting_started/accessing_an_instance/accessing_a_dcs_redis_4.0_or_5.0_instance_on_the_console.rst rename to umn/source/getting_started/accessing_an_instance/accessing_a_dcs_redis_4.0_5.0_6.0_instance_on_the_console.rst index fb0fe9f..50561b3 100644 --- a/umn/source/getting_started/accessing_an_instance/accessing_a_dcs_redis_4.0_or_5.0_instance_on_the_console.rst +++ b/umn/source/getting_started/accessing_an_instance/accessing_a_dcs_redis_4.0_5.0_6.0_instance_on_the_console.rst @@ -2,10 +2,10 @@ .. _dcs-ug-0312008: -Accessing a DCS Redis 4.0 or 5.0 Instance on the Console -======================================================== +Accessing a DCS Redis 4.0/5.0/6.0 Instance on the Console +========================================================= -Access a DCS Redis instance through Web CLI. This function is supported only by DCS Redis 4.0 and 5.0 instances, and not by DCS Redis 3.0 instances. +Access a DCS Redis instance through Web CLI. This function is supported only by DCS Redis 4.0 and later instances, and not by DCS Redis 3.0 instances. .. note:: @@ -16,7 +16,7 @@ Access a DCS Redis instance through Web CLI. This function is supported only by Prerequisites ------------- -The DCS Redis 4.0 or 5.0 instance you want to access through Web CLI is in the **Running** state. +The instance is in the **Running** state. Procedure --------- diff --git a/umn/source/getting_started/accessing_an_instance/accessing_a_dcs_redis_instance_through_redis-cli.rst b/umn/source/getting_started/accessing_an_instance/accessing_a_dcs_redis_instance_through_redis-cli.rst index 5a7915d..c94e683 100644 --- a/umn/source/getting_started/accessing_an_instance/accessing_a_dcs_redis_instance_through_redis-cli.rst +++ b/umn/source/getting_started/accessing_an_instance/accessing_a_dcs_redis_instance_through_redis-cli.rst @@ -9,13 +9,13 @@ Access a DCS Redis instance through redis-cli on an ECS in the same VPC. For mor .. note:: - - Redis 3.0 does not support port customization and allows only port 6379. For Redis 4.0 and 5.0, you can specify a port or use the default port 6379. The following uses the default port 6379. If you have specified a port, replace 6379 with the actual port. + - Redis 3.0 does not support port customization and allows only port 6379. For Redis 4.0 and later, you can specify a port or use the default port 6379. The following uses the default port 6379. If you have specified a port, replace 6379 with the actual port. - **When connecting to a Redis Cluster instance, ensure that** **-c** **is added to the command.** Otherwise, the connection will fail. - Run the following command to connect to a Redis Cluster instance: - ./redis-cli -h *{dcs_instance_address}* -p 6379 -a *{password}* **-c** + ./redis-cli -h *{dcs_instance_address}* -p *6379* -a *{password}* **-c** - Run the following command to connect to a single-node, master/standby, or Proxy Cluster instance: @@ -23,6 +23,16 @@ Access a DCS Redis instance through redis-cli on an ECS in the same VPC. For mor For details, see :ref:`3 ` and :ref:`4 `. + - If SSL is enabled for a DCS Redis 6.0 instance, set an SSL certificate path. + + - Run the following command to connect to a Redis Cluster instance: + + ./redis-cli -h *{dcs_instance_address}* -p *6379* -a *{password}* -c **--tls --cacert {certification file path}** + + - Run the following command to connect to a single-node, master/standby, or Proxy Cluster instance: + + *./redis-cli -h* *{dcs_instance_address} -p 6379* -a *{password}* **--tls --cacert {certification file path}** + Prerequisites ------------- @@ -65,7 +75,7 @@ Procedure (Linux) Access a DCS instance of a type other than Redis Cluster. - Perform the following procedure to access a DCS Redis 3.0 instance, or a single-node or master/standby DCS Redis 4.0 or 5.0 instance. + Perform the following procedure to access a single-node, master/standby instance. **./redis-cli -h** *${instance IP}* **-p 6379 -a** *${password}* diff --git a/umn/source/getting_started/accessing_an_instance/index.rst b/umn/source/getting_started/accessing_an_instance/index.rst index e2d0193..99526aa 100644 --- a/umn/source/getting_started/accessing_an_instance/index.rst +++ b/umn/source/getting_started/accessing_an_instance/index.rst @@ -7,7 +7,7 @@ Accessing an Instance - :ref:`Accessing a DCS Redis Instance Through redis-cli ` - :ref:`Access in Different Languages ` -- :ref:`Accessing a DCS Redis 4.0 or 5.0 Instance on the Console ` +- :ref:`Accessing a DCS Redis 4.0/5.0/6.0 Instance on the Console ` .. toctree:: :maxdepth: 1 @@ -15,4 +15,4 @@ Accessing an Instance accessing_a_dcs_redis_instance_through_redis-cli access_in_different_languages/index - accessing_a_dcs_redis_4.0_or_5.0_instance_on_the_console + accessing_a_dcs_redis_4.0_5.0_6.0_instance_on_the_console diff --git a/umn/source/getting_started/creating_an_instance/creating_a_dcs_redis_instance.rst b/umn/source/getting_started/creating_an_instance/creating_a_dcs_redis_instance.rst index 90cc2e7..20e09b5 100644 --- a/umn/source/getting_started/creating_an_instance/creating_a_dcs_redis_instance.rst +++ b/umn/source/getting_started/creating_an_instance/creating_a_dcs_redis_instance.rst @@ -31,7 +31,7 @@ Creating a DCS Redis Instance b. **Version**: - Currently, 3.0, 4.0, and 5.0 versions are supported. + Currently, versions 3.0/4.0/5.0/6.0 are supported. .. note:: @@ -44,7 +44,7 @@ Creating a DCS Redis Instance e. Set **Replicas**. The default value is **2** (including the master). - This parameter is displayed only when you select Redis 4.0 or Redis 5.0 and the instance type is master/standby or Redis Cluster. + This parameter is displayed only when you select Redis 4.0/5.0/6.0 and the instance type is master/standby or Redis Cluster. f. Select an AZ. @@ -67,13 +67,13 @@ Creating a DCS Redis Instance You can choose to obtain an automatically assigned IP address or manually specify an IP address that is available in the selected subnet. - For a DCS Redis 4.0 or 5.0 instance, you can specify a port numbering in the range from 1 to 65535. If no port is specified, the default port 6379 will be used. For a DCS Redis 3.0 instance, the port cannot be customized. Port 6379 will be used. + For a DCS Redis 4.0 or later instance, you can specify a port numbering in the range from 1 to 65535. If no port is specified, the default port 6379 will be used. For a DCS Redis 3.0 instance, the port cannot be customized. Port 6379 will be used. b. Select a security group. A security group is a set of rules that control access to ECSs. It provides access policies for mutually trusted ECSs with the same security protection requirements in the same VPC. - This parameter is displayed only for DCS Redis 3.0 instances. DCS Redis 4.0 and 5.0 instances are based on VPC endpoints and do not support security groups. To control access to a DCS Redis 4.0 or 5.0 instance, configure a whitelist after instance creation. For details, see :ref:`Managing IP Address Whitelist `. + This parameter is displayed only for DCS Redis 3.0 instances. DCS Redis 4.0/5.0/6.0 instances are based on VPC endpoints and do not support security groups. To control access to a DCS Redis 4.0/5.0/6.0 instance, configure a whitelist after instance creation. For details, see :ref:`Managing IP Address Whitelist `. #. Set the instance password. @@ -106,7 +106,7 @@ Creating a DCS Redis Instance c. Rename critical commands. - **Command Renaming** is displayed for Redis 4.0 and 5.0. Currently, you can only rename the **COMMAND**, **KEYS**, **FLUSHDB**, **FLUSHALL**, and **HGETALL** commands. + **Command Renaming** is displayed for Redis 4.0 and later. Currently, you can only rename the **COMMAND**, **KEYS**, **FLUSHDB**, and **FLUSHALL** commands. d. Specify the maintenance window. @@ -120,12 +120,7 @@ Creating a DCS Redis Instance #. Return to the **Cache Manager** page to view and manage your DCS instances. - a. Creating a single-node or master/standby DCS Redis 3.0 instance takes 5 to 15 minutes. Creating a cluster DCS Redis 3.0 instance takes 30 minutes. - - .. note:: - - DCS Redis 4.0 and 5.0 instances are containerized and can be created within seconds. - + a. Creating a single-node or master/standby DCS Redis 3.0 instance takes 5 to 15 minutes. Creating a cluster DCS Redis 3.0 instance takes 30 minutes.DCS Redis 4.0 and later instances are containerized and can be created within seconds. b. After a DCS instance has been successfully created, it enters the **Running** state by default. .. note:: diff --git a/umn/source/getting_started/viewing_details_of_a_dcs_instance.rst b/umn/source/getting_started/viewing_details_of_a_dcs_instance.rst index b32cc4b..bb7a747 100644 --- a/umn/source/getting_started/viewing_details_of_a_dcs_instance.rst +++ b/umn/source/getting_started/viewing_details_of_a_dcs_instance.rst @@ -34,52 +34,52 @@ Procedure .. table:: **Table 1** Parameters on the Basic Information page of a DCS instance - +-----------------------+----------------------------+--------------------------------------------------------------------------------------------------------------------------------------------------------+ - | Section | Parameter | Description | - +=======================+============================+========================================================================================================================================================+ - | Instance Details | Name | Name of the chosen instance. To modify the instance name, click the |image2| icon. | - +-----------------------+----------------------------+--------------------------------------------------------------------------------------------------------------------------------------------------------+ - | | Status | State of the chosen instance. | - +-----------------------+----------------------------+--------------------------------------------------------------------------------------------------------------------------------------------------------+ - | | ID | ID of the chosen instance. | - +-----------------------+----------------------------+--------------------------------------------------------------------------------------------------------------------------------------------------------+ - | | Cache Engine | Cache engine and cache engine version used by the DCS instance. For example, Redis 3.0. | - +-----------------------+----------------------------+--------------------------------------------------------------------------------------------------------------------------------------------------------+ - | | Instance Type | Type of the selected instance. Currently, supported types include single-node, master/standby, Proxy Cluster, and Redis Cluster. | - +-----------------------+----------------------------+--------------------------------------------------------------------------------------------------------------------------------------------------------+ - | | Cache Size | Specification of the chosen instance. | - +-----------------------+----------------------------+--------------------------------------------------------------------------------------------------------------------------------------------------------+ - | | Used/Available Memory (MB) | The used memory space and maximum available memory space of the chosen instance. | - | | | | - | | | The used memory space includes: | - | | | | - | | | - Size of data stored on the DCS instance | - | | | - Size of Redis-server buffers (including client buffer and repl-backlog) and internal data structures | - +-----------------------+----------------------------+--------------------------------------------------------------------------------------------------------------------------------------------------------+ - | | CPU | CPU of the DCS instance. | - +-----------------------+----------------------------+--------------------------------------------------------------------------------------------------------------------------------------------------------+ - | | Created | Time at which the chosen instance started to be created. | - +-----------------------+----------------------------+--------------------------------------------------------------------------------------------------------------------------------------------------------+ - | | Run | Time at which the instance was created. | - +-----------------------+----------------------------+--------------------------------------------------------------------------------------------------------------------------------------------------------+ - | | Maintenance | Time range for any scheduled maintenance activities on cache nodes of this DCS instance. To modify the time window, click the |image3| icon. | - +-----------------------+----------------------------+--------------------------------------------------------------------------------------------------------------------------------------------------------+ - | | Description | Description of the chosen DCS instance. To modify the description, click the |image4| icon. | - +-----------------------+----------------------------+--------------------------------------------------------------------------------------------------------------------------------------------------------+ - | Connection | Password Protected | Currently, password-protected access and password-free access are supported. | - +-----------------------+----------------------------+--------------------------------------------------------------------------------------------------------------------------------------------------------+ - | | IP Address | IP address and port number of the chosen instance. | - +-----------------------+----------------------------+--------------------------------------------------------------------------------------------------------------------------------------------------------+ - | Network | AZ | Availability zone in which the cache node running the selected DCS instance resides. | - +-----------------------+----------------------------+--------------------------------------------------------------------------------------------------------------------------------------------------------+ - | | VPC | VPC in which the chosen instance resides. | - +-----------------------+----------------------------+--------------------------------------------------------------------------------------------------------------------------------------------------------+ - | | Subnet | Subnet in which the chosen instance resides. | - +-----------------------+----------------------------+--------------------------------------------------------------------------------------------------------------------------------------------------------+ - | | Security Group | Security group that controls access to the chosen instance. To modify the security group, click the |image5| icon. | - | | | | - | | | This parameter is displayed only for DCS Redis 3.0 instances. DCS for Redis 4.0 and 5.0 are based on VPC endpoints and do not support security groups. | - +-----------------------+----------------------------+--------------------------------------------------------------------------------------------------------------------------------------------------------+ + +-----------------------+----------------------------+---------------------------------------------------------------------------------------------------------------------------------------------------+ + | Section | Parameter | Description | + +=======================+============================+===================================================================================================================================================+ + | Instance Details | Name | Name of the chosen instance. To modify the instance name, click the |image2| icon. | + +-----------------------+----------------------------+---------------------------------------------------------------------------------------------------------------------------------------------------+ + | | Status | State of the chosen instance. | + +-----------------------+----------------------------+---------------------------------------------------------------------------------------------------------------------------------------------------+ + | | ID | ID of the chosen instance. | + +-----------------------+----------------------------+---------------------------------------------------------------------------------------------------------------------------------------------------+ + | | Cache Engine | Cache engine and cache engine version used by the DCS instance. For example, Redis 3.0. | + +-----------------------+----------------------------+---------------------------------------------------------------------------------------------------------------------------------------------------+ + | | Instance Type | Type of the selected instance. Currently, supported types include single-node, master/standby, Proxy Cluster, and Redis Cluster. | + +-----------------------+----------------------------+---------------------------------------------------------------------------------------------------------------------------------------------------+ + | | Cache Size | Specification of the chosen instance. | + +-----------------------+----------------------------+---------------------------------------------------------------------------------------------------------------------------------------------------+ + | | Used/Available Memory (MB) | The used memory space and maximum available memory space of the chosen instance. | + | | | | + | | | The used memory space includes: | + | | | | + | | | - Size of data stored on the DCS instance | + | | | - Size of Redis-server buffers (including client buffer and repl-backlog) and internal data structures | + +-----------------------+----------------------------+---------------------------------------------------------------------------------------------------------------------------------------------------+ + | | CPU | CPU of the DCS instance. | + +-----------------------+----------------------------+---------------------------------------------------------------------------------------------------------------------------------------------------+ + | | Created | Time at which the chosen instance started to be created. | + +-----------------------+----------------------------+---------------------------------------------------------------------------------------------------------------------------------------------------+ + | | Run | Time at which the instance was created. | + +-----------------------+----------------------------+---------------------------------------------------------------------------------------------------------------------------------------------------+ + | | Maintenance | Time range for any scheduled maintenance activities on cache nodes of this DCS instance. To modify the time window, click the |image3| icon. | + +-----------------------+----------------------------+---------------------------------------------------------------------------------------------------------------------------------------------------+ + | | Description | Description of the chosen DCS instance. To modify the description, click the |image4| icon. | + +-----------------------+----------------------------+---------------------------------------------------------------------------------------------------------------------------------------------------+ + | Connection | Password Protected | Currently, password-protected access and password-free access are supported. | + +-----------------------+----------------------------+---------------------------------------------------------------------------------------------------------------------------------------------------+ + | | IP Address | IP address and port number of the chosen instance. | + +-----------------------+----------------------------+---------------------------------------------------------------------------------------------------------------------------------------------------+ + | Network | AZ | Availability zone in which the cache node running the selected DCS instance resides. | + +-----------------------+----------------------------+---------------------------------------------------------------------------------------------------------------------------------------------------+ + | | VPC | VPC in which the chosen instance resides. | + +-----------------------+----------------------------+---------------------------------------------------------------------------------------------------------------------------------------------------+ + | | Subnet | Subnet in which the chosen instance resides. | + +-----------------------+----------------------------+---------------------------------------------------------------------------------------------------------------------------------------------------+ + | | Security Group | Security group that controls access to the chosen instance. To modify the security group, click the |image5| icon. | + | | | | + | | | This parameter is displayed only for DCS Redis 3.0 instances. Other Redis versions are based on VPC endpoints and do not support security groups. | + +-----------------------+----------------------------+---------------------------------------------------------------------------------------------------------------------------------------------------+ .. |image1| image:: /_static/images/en-us_image_0000001194522893.png .. |image2| image:: /_static/images/en-us_image_0266235362.png diff --git a/umn/source/monitoring/dcs_metrics.rst b/umn/source/monitoring/dcs_metrics.rst index cf9e4bc..f493550 100644 --- a/umn/source/monitoring/dcs_metrics.rst +++ b/umn/source/monitoring/dcs_metrics.rst @@ -36,689 +36,289 @@ DCS Redis 3.0 Instance Metrics .. note:: - The **Monitored Objects and Dimensions** column lists instances and dimensions that support the corresponding metrics. + - The **Monitored Object** column lists instances that support the corresponding metrics. + - :ref:`Dimensions ` lists the metric dimensions. .. table:: **Table 1** DCS Redis 3.0 instance metrics +----------------------------+----------------------------+----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+---------------+------------------------------------------------------------+------------------------------+ - | Metric ID | Metric | Description | Value Range | Monitored Object and Dimension | Monitoring Period (Raw Data) | + | Metric ID | Metric | Description | Value Range | Monitored Object | Monitoring Period (Raw Data) | +============================+============================+========================================================================================================================================================================================+===============+============================================================+==============================+ - | cpu_usage | CPU Usage | The monitored object's maximum CPU usage among multiple sampling values in a monitoring period | 0-100% | Monitored object: | 1 minute | + | cpu_usage | CPU Usage | The monitored object's maximum CPU usage among multiple sampling values in a monitoring period | 0-100% | Single-node, master/standby, or cluster DCS Redis instance | 1 minute | | | | | | | | - | | | Unit: % | | Single-node, master/standby, or cluster DCS Redis instance | | - | | | | | | | - | | | | | Dimension: | | - | | | | | | | - | | | | | dcs_instance_id | | + | | | Unit: % | | | | +----------------------------+----------------------------+----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+---------------+------------------------------------------------------------+------------------------------+ - | memory_usage | Memory Usage | Memory consumed by the monitored object | 0-100% | Monitored object: | 1 minute | + | memory_usage | Memory Usage | Memory consumed by the monitored object | 0-100% | Single-node, master/standby, or cluster DCS Redis instance | 1 minute | | | | | | | | - | | | Unit: % | | Single-node, master/standby, or cluster DCS Redis instance | | - | | | | | | | - | | | | | Dimension: | | - | | | | | | | - | | | | | dcs_instance_id | | + | | | Unit: % | | | | +----------------------------+----------------------------+----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+---------------+------------------------------------------------------------+------------------------------+ - | net_in_throughput | Network Input Throughput | Inbound throughput per second on a port | >= 0 | Monitored object: | 1 minute | + | net_in_throughput | Network Input Throughput | Inbound throughput per second on a port | >= 0 | Single-node, master/standby, or cluster DCS Redis instance | 1 minute | | | | | | | | - | | | Unit: byte/s | | Single-node, master/standby, or cluster DCS Redis instance | | - | | | | | | | - | | | | | Dimension: | | - | | | | | | | - | | | | | dcs_instance_id | | + | | | Unit: byte/s | | | | +----------------------------+----------------------------+----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+---------------+------------------------------------------------------------+------------------------------+ - | net_out_throughput | Network Output Throughput | Outbound throughput per second on a port | >= 0 | Monitored object: | 1 minute | + | net_out_throughput | Network Output Throughput | Outbound throughput per second on a port | >= 0 | Single-node, master/standby, or cluster DCS Redis instance | 1 minute | | | | | | | | - | | | Unit: byte/s | | Single-node, master/standby, or cluster DCS Redis instance | | - | | | | | | | - | | | | | Dimension: | | - | | | | | | | - | | | | | dcs_instance_id | | + | | | Unit: byte/s | | | | +----------------------------+----------------------------+----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+---------------+------------------------------------------------------------+------------------------------+ - | node_status | Instance Node Status | Status of instance nodes. If the status is normal, the value is **0**. If the status is abnormal, the value is **1**. | ``-`` | Monitored object: | 1 minute | - | | | | | | | - | | | | | Single-node, master/standby, or cluster DCS Redis instance | | - | | | | | | | - | | | | | Dimension: | | - | | | | | | | - | | | | | dcs_instance_id | | + | node_status | Instance Node Status | Status of instance nodes. If the status is normal, the value is **0**. If the status is abnormal, the value is **1**. | ``-`` | Single-node, master/standby, or cluster DCS Redis instance | 1 minute | +----------------------------+----------------------------+----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+---------------+------------------------------------------------------------+------------------------------+ - | connected_clients | Connected Clients | Number of connected clients (excluding those from slave nodes) | >= 0 | Monitored object: | 1 minute | - | | | | | | | - | | | | | Single-node, master/standby, or cluster DCS Redis instance | | - | | | | | | | - | | | | | Dimension: | | - | | | | | | | - | | | | | dcs_instance_id | | + | connected_clients | Connected Clients | Number of connected clients (excluding those from slave nodes) | >= 0 | Single-node, master/standby, or cluster DCS Redis instance | 1 minute | +----------------------------+----------------------------+----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+---------------+------------------------------------------------------------+------------------------------+ - | client_longest_out_list | Client Longest Output List | Longest output list among current client connections | >= 0 | Monitored object: | 1 minute | - | | | | | | | - | | | | | Single-node, master/standby, or cluster DCS Redis instance | | - | | | | | | | - | | | | | Dimension: | | - | | | | | | | - | | | | | dcs_instance_id | | + | client_longest_out_list | Client Longest Output List | Longest output list among current client connections | >= 0 | Single-node, master/standby, or cluster DCS Redis instance | 1 minute | +----------------------------+----------------------------+----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+---------------+------------------------------------------------------------+------------------------------+ - | client_biggest_in_buf | Client Biggest Input Buf | Maximum input data length among current client connections | >= 0 | Monitored object: | 1 minute | + | client_biggest_in_buf | Client Biggest Input Buf | Maximum input data length among current client connections | >= 0 | Single-node, master/standby, or cluster DCS Redis instance | 1 minute | | | | | | | | - | | | Unit: byte | | Single-node, master/standby, or cluster DCS Redis instance | | - | | | | | | | - | | | | | Dimension: | | - | | | | | | | - | | | | | dcs_instance_id | | + | | | Unit: byte | | | | +----------------------------+----------------------------+----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+---------------+------------------------------------------------------------+------------------------------+ - | blocked_clients | Blocked Clients | Number of clients suspended by block operations such as BLPOP, BRPOP, and BRPOPLPUSH | >= 0 | Monitored object: | 1 minute | - | | | | | | | - | | | | | Single-node, master/standby, or cluster DCS Redis instance | | - | | | | | | | - | | | | | Dimension: | | - | | | | | | | - | | | | | dcs_instance_id | | + | blocked_clients | Blocked Clients | Number of clients suspended by block operations such as BLPOP, BRPOP, and BRPOPLPUSH | >= 0 | Single-node, master/standby, or cluster DCS Redis instance | 1 minute | +----------------------------+----------------------------+----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+---------------+------------------------------------------------------------+------------------------------+ - | used_memory | Used Memory | Number of bytes used by the Redis server | >= 0 | Monitored object: | 1 minute | + | used_memory | Used Memory | Number of bytes used by the Redis server | >= 0 | Single-node, master/standby, or cluster DCS Redis instance | 1 minute | | | | | | | | - | | | Unit: byte | | Single-node, master/standby, or cluster DCS Redis instance | | - | | | | | | | - | | | | | Dimension: | | - | | | | | | | - | | | | | dcs_instance_id | | + | | | Unit: byte | | | | +----------------------------+----------------------------+----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+---------------+------------------------------------------------------------+------------------------------+ - | used_memory_rss | Used Memory RSS | Resident set size (RSS) memory that the Redis server has used, which is the memory that actually resides in the memory, including all stack and heap memory but not swapped-out memory | >= 0 | Monitored object: | 1 minute | + | used_memory_rss | Used Memory RSS | Resident set size (RSS) memory that the Redis server has used, which is the memory that actually resides in the memory, including all stack and heap memory but not swapped-out memory | >= 0 | Single-node, master/standby, or cluster DCS Redis instance | 1 minute | | | | | | | | - | | | Unit: byte | | Single-node, master/standby, or cluster DCS Redis instance | | - | | | | | | | - | | | | | Dimension: | | - | | | | | | | - | | | | | dcs_instance_id | | + | | | Unit: byte | | | | +----------------------------+----------------------------+----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+---------------+------------------------------------------------------------+------------------------------+ - | used_memory_peak | Used Memory Peak | Peak memory consumed by Redis since the Redis server last started | >= 0 | Monitored object: | 1 minute | + | used_memory_peak | Used Memory Peak | Peak memory consumed by Redis since the Redis server last started | >= 0 | Single-node, master/standby, or cluster DCS Redis instance | 1 minute | | | | | | | | - | | | Unit: byte | | Single-node, master/standby, or cluster DCS Redis instance | | - | | | | | | | - | | | | | Dimension: | | - | | | | | | | - | | | | | dcs_instance_id | | + | | | Unit: byte | | | | +----------------------------+----------------------------+----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+---------------+------------------------------------------------------------+------------------------------+ - | used_memory_lua | Used Memory Lua | Number of bytes used by the Lua engine | >= 0 | Monitored object: | 1 minute | + | used_memory_lua | Used Memory Lua | Number of bytes used by the Lua engine | >= 0 | Single-node, master/standby, or cluster DCS Redis instance | 1 minute | | | | | | | | - | | | Unit: byte | | Single-node, master/standby, or cluster DCS Redis instance | | - | | | | | | | - | | | | | Dimension: | | - | | | | | | | - | | | | | dcs_instance_id | | + | | | Unit: byte | | | | +----------------------------+----------------------------+----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+---------------+------------------------------------------------------------+------------------------------+ - | memory_frag_ratio | Memory Fragmentation Ratio | Current memory fragmentation, which is the ratio between **used_memory_rss**/**used_memory**. | >= 0 | Monitored object: | 1 minute | - | | | | | | | - | | | | | Single-node, master/standby, or cluster DCS Redis instance | | - | | | | | | | - | | | | | Dimension: | | - | | | | | | | - | | | | | dcs_instance_id | | + | memory_frag_ratio | Memory Fragmentation Ratio | Current memory fragmentation, which is the ratio between **used_memory_rss**/**used_memory**. | >= 0 | Single-node, master/standby, or cluster DCS Redis instance | 1 minute | +----------------------------+----------------------------+----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+---------------+------------------------------------------------------------+------------------------------+ - | total_connections_received | New Connections | Number of connections received during the monitoring period | >= 0 | Monitored object: | 1 minute | - | | | | | | | - | | | | | Single-node, master/standby, or cluster DCS Redis instance | | - | | | | | | | - | | | | | Dimension: | | - | | | | | | | - | | | | | dcs_instance_id | | + | total_connections_received | New Connections | Number of connections received during the monitoring period | >= 0 | Single-node, master/standby, or cluster DCS Redis instance | 1 minute | +----------------------------+----------------------------+----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+---------------+------------------------------------------------------------+------------------------------+ - | total_commands_processed | Commands Processed | Number of commands processed during the monitoring period | >= 0 | Monitored object: | 1 minute | - | | | | | | | - | | | | | Single-node, master/standby, or cluster DCS Redis instance | | - | | | | | | | - | | | | | Dimension: | | - | | | | | | | - | | | | | dcs_instance_id | | + | total_commands_processed | Commands Processed | Number of commands processed during the monitoring period | >= 0 | Single-node, master/standby, or cluster DCS Redis instance | 1 minute | +----------------------------+----------------------------+----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+---------------+------------------------------------------------------------+------------------------------+ - | instantaneous_ops | Ops per Second | Number of commands processed per second | >= 0 | Monitored object: | 1 minute | - | | | | | | | - | | | | | Single-node, master/standby, or cluster DCS Redis instance | | - | | | | | | | - | | | | | Dimension: | | - | | | | | | | - | | | | | dcs_instance_id | | + | instantaneous_ops | Ops per Second | Number of commands processed per second | >= 0 | Single-node, master/standby, or cluster DCS Redis instance | 1 minute | +----------------------------+----------------------------+----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+---------------+------------------------------------------------------------+------------------------------+ - | total_net_input_bytes | Network Input Bytes | Number of bytes received during the monitoring period | >= 0 | Monitored object: | 1 minute | + | total_net_input_bytes | Network Input Bytes | Number of bytes received during the monitoring period | >= 0 | Single-node, master/standby, or cluster DCS Redis instance | 1 minute | | | | | | | | - | | | Unit: byte | | Single-node, master/standby, or cluster DCS Redis instance | | - | | | | | | | - | | | | | Dimension: | | - | | | | | | | - | | | | | dcs_instance_id | | + | | | Unit: byte | | | | +----------------------------+----------------------------+----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+---------------+------------------------------------------------------------+------------------------------+ - | total_net_output_bytes | Network Output Bytes | Number of bytes sent during the monitoring period | >= 0 | Monitored object: | 1 minute | + | total_net_output_bytes | Network Output Bytes | Number of bytes sent during the monitoring period | >= 0 | Single-node, master/standby, or cluster DCS Redis instance | 1 minute | | | | | | | | - | | | Unit: byte | | Single-node, master/standby, or cluster DCS Redis instance | | - | | | | | | | - | | | | | Dimension: | | - | | | | | | | - | | | | | dcs_instance_id | | + | | | Unit: byte | | | | +----------------------------+----------------------------+----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+---------------+------------------------------------------------------------+------------------------------+ - | instantaneous_input_kbps | Input Flow | Instantaneous input traffic | >= 0 kbits/s | Monitored object: | 1 minute | + | instantaneous_input_kbps | Input Flow | Instantaneous input traffic | >= 0 kbits/s | Single-node, master/standby, or cluster DCS Redis instance | 1 minute | | | | | | | | - | | | Unit: kbit/s | | Single-node, master/standby, or cluster DCS Redis instance | | - | | | | | | | - | | | | | Dimension: | | - | | | | | | | - | | | | | dcs_instance_id | | + | | | Unit: kbit/s | | | | +----------------------------+----------------------------+----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+---------------+------------------------------------------------------------+------------------------------+ - | instantaneous_output_kbps | Output Flow | Instantaneous output traffic | >= 0 kbits/s | Monitored object: | 1 minute | + | instantaneous_output_kbps | Output Flow | Instantaneous output traffic | >= 0 kbits/s | Single-node, master/standby, or cluster DCS Redis instance | 1 minute | | | | | | | | - | | | Unit: kbit/s | | Single-node, master/standby, or cluster DCS Redis instance | | - | | | | | | | - | | | | | Dimension: | | - | | | | | | | - | | | | | dcs_instance_id | | + | | | Unit: kbit/s | | | | +----------------------------+----------------------------+----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+---------------+------------------------------------------------------------+------------------------------+ - | rejected_connections | Rejected Connections | Number of connections that have exceeded maxclients and been rejected during the monitoring period | >= 0 | Monitored object: | 1 minute | - | | | | | | | - | | | | | Single-node, master/standby, or cluster DCS Redis instance | | - | | | | | | | - | | | | | Dimension: | | - | | | | | | | - | | | | | dcs_instance_id | | + | rejected_connections | Rejected Connections | Number of connections that have exceeded maxclients and been rejected during the monitoring period | >= 0 | Single-node, master/standby, or cluster DCS Redis instance | 1 minute | +----------------------------+----------------------------+----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+---------------+------------------------------------------------------------+------------------------------+ - | expired_keys | Expired Keys | Number of keys that have expired and been deleted during the monitoring period | >= 0 | Monitored object: | 1 minute | - | | | | | | | - | | | | | Single-node, master/standby, or cluster DCS Redis instance | | - | | | | | | | - | | | | | Dimension: | | - | | | | | | | - | | | | | dcs_instance_id | | + | expired_keys | Expired Keys | Number of keys that have expired and been deleted during the monitoring period | >= 0 | Single-node, master/standby, or cluster DCS Redis instance | 1 minute | +----------------------------+----------------------------+----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+---------------+------------------------------------------------------------+------------------------------+ - | evicted_keys | Evicted Keys | Number of keys that have been evicted and deleted during the monitoring period | >= 0 | Monitored object: | 1 minute | - | | | | | | | - | | | | | Single-node, master/standby, or cluster DCS Redis instance | | - | | | | | | | - | | | | | Dimension: | | - | | | | | | | - | | | | | dcs_instance_id | | + | evicted_keys | Evicted Keys | Number of keys that have been evicted and deleted during the monitoring period | >= 0 | Single-node, master/standby, or cluster DCS Redis instance | 1 minute | +----------------------------+----------------------------+----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+---------------+------------------------------------------------------------+------------------------------+ - | keyspace_hits | Keyspace Hits | Number of successful lookups of keys in the main dictionary during the monitoring period | >= 0 | Monitored object: | 1 minute | - | | | | | | | - | | | | | Single-node, master/standby, or cluster DCS Redis instance | | - | | | | | | | - | | | | | Dimension: | | - | | | | | | | - | | | | | dcs_instance_id | | + | keyspace_hits | Keyspace Hits | Number of successful lookups of keys in the main dictionary during the monitoring period | >= 0 | Single-node, master/standby, or cluster DCS Redis instance | 1 minute | +----------------------------+----------------------------+----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+---------------+------------------------------------------------------------+------------------------------+ - | keyspace_misses | Keyspace Misses | Number of failed lookups of keys in the main dictionary during the monitoring period | >= 0 | Monitored object: | 1 minute | - | | | | | | | - | | | | | Single-node, master/standby, or cluster DCS Redis instance | | - | | | | | | | - | | | | | Dimension: | | - | | | | | | | - | | | | | dcs_instance_id | | + | keyspace_misses | Keyspace Misses | Number of failed lookups of keys in the main dictionary during the monitoring period | >= 0 | Single-node, master/standby, or cluster DCS Redis instance | 1 minute | +----------------------------+----------------------------+----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+---------------+------------------------------------------------------------+------------------------------+ - | pubsub_channels | PubSub Channels | Number of Pub/Sub channels | >= 0 | Monitored object: | 1 minute | - | | | | | | | - | | | | | Single-node, master/standby, or cluster DCS Redis instance | | - | | | | | | | - | | | | | Dimension: | | - | | | | | | | - | | | | | dcs_instance_id | | + | pubsub_channels | PubSub Channels | Number of Pub/Sub channels | >= 0 | Single-node, master/standby, or cluster DCS Redis instance | 1 minute | +----------------------------+----------------------------+----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+---------------+------------------------------------------------------------+------------------------------+ - | pubsub_patterns | PubSub Patterns | Number of Pub/Sub patterns | >= 0 | Monitored object: | 1 minute | - | | | | | | | - | | | | | Single-node, master/standby, or cluster DCS Redis instance | | - | | | | | | | - | | | | | Dimension: | | - | | | | | | | - | | | | | dcs_instance_id | | + | pubsub_patterns | PubSub Patterns | Number of Pub/Sub patterns | >= 0 | Single-node, master/standby, or cluster DCS Redis instance | 1 minute | +----------------------------+----------------------------+----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+---------------+------------------------------------------------------------+------------------------------+ - | keyspace_hits_perc | Hit Rate | Ratio of the number of Redis cache hits to the number of lookups. Calculation: keyspace_hits/(keyspace_hits + keyspace_misses) | 0-100% | Monitored object: | 1 minute | + | keyspace_hits_perc | Hit Rate | Ratio of the number of Redis cache hits to the number of lookups. Calculation: keyspace_hits/(keyspace_hits + keyspace_misses) | 0-100% | Single-node, master/standby, or cluster DCS Redis instance | 1 minute | | | | | | | | - | | | Unit: % | | Single-node, master/standby, or cluster DCS Redis instance | | - | | | | | | | - | | | | | Dimension: | | - | | | | | | | - | | | | | dcs_instance_id | | + | | | Unit: % | | | | +----------------------------+----------------------------+----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+---------------+------------------------------------------------------------+------------------------------+ - | command_max_delay | Maximum Command Latency | Maximum latency of commands | >= 0 ms | Monitored object: | 1 minute | + | command_max_delay | Maximum Command Latency | Maximum latency of commands | >= 0 ms | Single-node, master/standby, or cluster DCS Redis instance | 1 minute | | | | | | | | - | | | Unit: ms | | Single-node, master/standby, or cluster DCS Redis instance | | - | | | | | | | - | | | | | Dimension: | | - | | | | | | | - | | | | | dcs_instance_id | | + | | | Unit: ms | | | | +----------------------------+----------------------------+----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+---------------+------------------------------------------------------------+------------------------------+ - | auth_errors | Authentication Failures | Number of failed authentications | >= 0 | Monitored object: | 1 minute | - | | | | | | | - | | | | | Single-node or master/standby DCS Redis instance | | - | | | | | | | - | | | | | Dimension: | | - | | | | | | | - | | | | | dcs_instance_id | | + | auth_errors | Authentication Failures | Number of failed authentications | >= 0 | Single-node or master/standby DCS Redis instance | 1 minute | +----------------------------+----------------------------+----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+---------------+------------------------------------------------------------+------------------------------+ - | is_slow_log_exist | Slow Query Logs | Existence of slow query logs in the instance | - **1**: yes | Monitored object: | 1 minute | + | is_slow_log_exist | Slow Query Logs | Existence of slow query logs in the instance | - **1**: yes | Single-node or master/standby DCS Redis instance | 1 minute | | | | | - **0**: no | | | - | | | | | Single-node or master/standby DCS Redis instance | | - | | | | | | | - | | | | | Dimension: | | - | | | | | | | - | | | | | dcs_instance_id | | +----------------------------+----------------------------+----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+---------------+------------------------------------------------------------+------------------------------+ - | keys | Keys | Number of keys in Redis | >= 0 | Monitored object: | 1 minute | - | | | | | | | - | | | | | Single-node or master/standby DCS Redis instance | | - | | | | | | | - | | | | | Dimension: | | - | | | | | | | - | | | | | dcs_instance_id | | + | keys | Keys | Number of keys in Redis | >= 0 | Single-node or master/standby DCS Redis instance | 1 minute | +----------------------------+----------------------------+----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+---------------+------------------------------------------------------------+------------------------------+ -DCS Redis 4.0 and 5.0 Instance Metrics +DCS Redis 4.0/5.0/6.0 Instance Metrics -------------------------------------- .. note:: - The **Monitored Objects and Dimensions** column lists instances and dimensions that support the corresponding metrics. + - The **Monitored Object** column lists instances that support the corresponding metrics. + - :ref:`Dimensions ` lists the metric dimensions. -.. table:: **Table 2** DCS Redis 4.0 and 5.0 instance metrics +.. table:: **Table 2** DCS Redis 4.0/5.0/6.0 instance metrics +----------------------------+----------------------------+----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+---------------+------------------------------------------------------------+------------------------------+ - | Metric ID | Metric | Description | Value Range | Monitored Object and Dimension | Monitoring Period (Raw Data) | + | Metric ID | Metric | Description | Value Range | Monitored Object | Monitoring Period (Raw Data) | +============================+============================+========================================================================================================================================================================================+===============+============================================================+==============================+ - | cpu_usage | CPU Usage | The monitored object's maximum CPU usage among multiple sampling values in a monitoring period | 0-100% | Monitored object: | 1 minute | + | cpu_usage | CPU Usage | The monitored object's maximum CPU usage among multiple sampling values in a monitoring period | 0-100% | Single-node or master/standby DCS Redis instance | 1 minute | | | | | | | | - | | | Unit: % | | Single-node or master/standby DCS Redis instance | | - | | | | | | | - | | | | | Dimension: | | - | | | | | | | - | | | | | dcs_instance_id | | + | | | Unit: % | | | | +----------------------------+----------------------------+----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+---------------+------------------------------------------------------------+------------------------------+ - | command_max_delay | Maximum Command Latency | Maximum latency of commands | >= 0 ms | Monitored object: | 1 minute | + | command_max_delay | Maximum Command Latency | Maximum latency of commands | >= 0 ms | Single-node, master/standby, or cluster DCS Redis instance | 1 minute | | | | | | | | - | | | Unit: ms | | Single-node, master/standby, or cluster DCS Redis instance | | - | | | | | | | - | | | | | Dimension: | | - | | | | | | | - | | | | | dcs_instance_id | | + | | | Unit: ms | | | | +----------------------------+----------------------------+----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+---------------+------------------------------------------------------------+------------------------------+ - | total_connections_received | New Connections | Number of connections received during the monitoring period | >= 0 | Monitored object: | 1 minute | - | | | | | | | - | | | | | Single-node, master/standby, or cluster DCS Redis instance | | - | | | | | | | - | | | | | Dimension: | | - | | | | | | | - | | | | | dcs_instance_id | | + | total_connections_received | New Connections | Number of connections received during the monitoring period | >= 0 | Single-node, master/standby, or cluster DCS Redis instance | 1 minute | +----------------------------+----------------------------+----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+---------------+------------------------------------------------------------+------------------------------+ - | is_slow_log_exist | Slow Query Logs | Existence of slow query logs in the instance | - **1**: yes | Monitored object: | 1 minute | + | is_slow_log_exist | Slow Query Logs | Existence of slow query logs in the instance | - **1**: yes | Single-node, master/standby, or cluster DCS Redis instance | 1 minute | | | | | - **0**: no | | | - | | | | | Single-node, master/standby, or cluster DCS Redis instance | | - | | | | | | | - | | | | | Dimension: | | - | | | | | | | - | | | | | dcs_instance_id | | +----------------------------+----------------------------+----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+---------------+------------------------------------------------------------+------------------------------+ - | memory_usage | Memory Usage | Memory consumed by the monitored object | 0-100% | Monitored object: | 1 minute | + | memory_usage | Memory Usage | Memory consumed by the monitored object | 0-100% | Single-node, master/standby, or cluster DCS Redis instance | 1 minute | | | | | | | | - | | | Unit: % | | Single-node, master/standby, or cluster DCS Redis instance | | - | | | | | | | - | | | | | Dimension: | | - | | | | | | | - | | | | | dcs_instance_id | | + | | | Unit: % | | | | +----------------------------+----------------------------+----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+---------------+------------------------------------------------------------+------------------------------+ - | expires | Keys With an Expiration | Number of keys with an expiration in Redis | >= 0 | Monitored object: | 1 minute | - | | | | | | | - | | | | | Single-node, master/standby, or cluster DCS Redis instance | | - | | | | | | | - | | | | | Dimension: | | - | | | | | | | - | | | | | dcs_instance_id | | + | expires | Keys With an Expiration | Number of keys with an expiration in Redis | >= 0 | Single-node, master/standby, or cluster DCS Redis instance | 1 minute | +----------------------------+----------------------------+----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+---------------+------------------------------------------------------------+------------------------------+ - | keyspace_hits_perc | Hit Rate | Ratio of the number of Redis cache hits to the number of lookups. Calculation: keyspace_hits/(keyspace_hits + keyspace_misses) | 0-100% | Monitored object: | 1 minute | + | keyspace_hits_perc | Hit Rate | Ratio of the number of Redis cache hits to the number of lookups. Calculation: keyspace_hits/(keyspace_hits + keyspace_misses) | 0-100% | Single-node, master/standby, or cluster DCS Redis instance | 1 minute | | | | | | | | - | | | Unit: % | | Single-node, master/standby, or cluster DCS Redis instance | | - | | | | | | | - | | | | | Dimension: | | - | | | | | | | - | | | | | dcs_instance_id | | + | | | Unit: % | | | | +----------------------------+----------------------------+----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+---------------+------------------------------------------------------------+------------------------------+ - | used_memory | Used Memory | Number of bytes used by the Redis server | >= 0 | Monitored object: | 1 minute | + | used_memory | Used Memory | Number of bytes used by the Redis server | >= 0 | Single-node, master/standby, or cluster DCS Redis instance | 1 minute | | | | | | | | - | | | Unit: byte | | Single-node, master/standby, or cluster DCS Redis instance | | - | | | | | | | - | | | | | Dimension: | | - | | | | | | | - | | | | | dcs_instance_id | | + | | | Unit: byte | | | | +----------------------------+----------------------------+----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+---------------+------------------------------------------------------------+------------------------------+ - | used_memory_dataset | Used Memory Dataset | Dataset memory that the Redis server has used | >= 0 | Monitored object: | 1 minute | + | used_memory_dataset | Used Memory Dataset | Dataset memory that the Redis server has used | >= 0 | Single-node, master/standby, or cluster DCS Redis instance | 1 minute | | | | | | | | - | | | Unit: byte | | Single-node, master/standby, or cluster DCS Redis instance | | - | | | | | | | - | | | | | Dimension: | | - | | | | | | | - | | | | | dcs_instance_id | | + | | | Unit: byte | | | | +----------------------------+----------------------------+----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+---------------+------------------------------------------------------------+------------------------------+ - | used_memory_dataset_perc | Used Memory Dataset Ratio | Percentage of dataset memory that the Redis server has used | 0-100% | Monitored object: | 1 minute | + | used_memory_dataset_perc | Used Memory Dataset Ratio | Percentage of dataset memory that the Redis server has used | 0-100% | Single-node, master/standby, or cluster DCS Redis instance | 1 minute | | | | | | | | - | | | Unit: % | | Single-node, master/standby, or cluster DCS Redis instance | | - | | | | | | | - | | | | | Dimension: | | - | | | | | | | - | | | | | dcs_instance_id | | + | | | Unit: % | | | | +----------------------------+----------------------------+----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+---------------+------------------------------------------------------------+------------------------------+ - | used_memory_rss | Used Memory RSS | Resident set size (RSS) memory that the Redis server has used, which is the memory that actually resides in the memory, including all stack and heap memory but not swapped-out memory | >= 0 | Monitored object: | 1 minute | + | used_memory_rss | Used Memory RSS | Resident set size (RSS) memory that the Redis server has used, which is the memory that actually resides in the memory, including all stack and heap memory but not swapped-out memory | >= 0 | Single-node, master/standby, or cluster DCS Redis instance | 1 minute | | | | | | | | - | | | Unit: byte | | Single-node, master/standby, or cluster DCS Redis instance | | - | | | | | | | - | | | | | Dimension: | | - | | | | | | | - | | | | | dcs_instance_id | | + | | | Unit: byte | | | | +----------------------------+----------------------------+----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+---------------+------------------------------------------------------------+------------------------------+ - | instantaneous_ops | Ops per Second | Number of commands processed per second | >= 0 | Monitored object: | 1 minute | - | | | | | | | - | | | | | Single-node, master/standby, or cluster DCS Redis instance | | - | | | | | | | - | | | | | Dimension: | | - | | | | | | | - | | | | | dcs_instance_id | | + | instantaneous_ops | Ops per Second | Number of commands processed per second | >= 0 | Single-node, master/standby, or cluster DCS Redis instance | 1 minute | +----------------------------+----------------------------+----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+---------------+------------------------------------------------------------+------------------------------+ - | keyspace_misses | Keyspace Misses | Number of failed lookups of keys in the main dictionary during the monitoring period | >= 0 | Monitored object: | 1 minute | - | | | | | | | - | | | | | Single-node, master/standby, or cluster DCS Redis instance | | - | | | | | | | - | | | | | Dimension: | | - | | | | | | | - | | | | | dcs_instance_id | | + | keyspace_misses | Keyspace Misses | Number of failed lookups of keys in the main dictionary during the monitoring period | >= 0 | Single-node, master/standby, or cluster DCS Redis instance | 1 minute | +----------------------------+----------------------------+----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+---------------+------------------------------------------------------------+------------------------------+ - | keys | Keys | Number of keys in Redis | >= 0 | Monitored object: | 1 minute | - | | | | | | | - | | | | | Single-node, master/standby, or cluster DCS Redis instance | | - | | | | | | | - | | | | | Dimension: | | - | | | | | | | - | | | | | dcs_instance_id | | + | keys | Keys | Number of keys in Redis | >= 0 | Single-node, master/standby, or cluster DCS Redis instance | 1 minute | +----------------------------+----------------------------+----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+---------------+------------------------------------------------------------+------------------------------+ - | rx_controlled | Flow Control Times | Number of flow control times during the monitoring period | >= 0 | Monitored object: | 1 minute | + | rx_controlled | Flow Control Times | Number of flow control times during the monitoring period | >= 0 | Single-node, master/standby, or cluster DCS Redis instance | 1 minute | | | | | | | | - | | | Unit: count/s | | Single-node, master/standby, or cluster DCS Redis instance | | - | | | | | | | - | | | | | Dimension: | | - | | | | | | | - | | | | | dcs_instance_id | | + | | | Unit: count/s | | | | +----------------------------+----------------------------+----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+---------------+------------------------------------------------------------+------------------------------+ - | bandwidth_usage | Bandwidth Usage | Percentage of the maximum bandwidth limit used (the average value of the sum of input and output flows) | >= 0 | Monitored object: | 1 minute | + | bandwidth_usage | Bandwidth Usage | Percentage of the maximum bandwidth limit used (the average value of the sum of input and output flows) | >= 0 | Single-node, master/standby, or cluster DCS Redis instance | 1 minute | | | | | | | | - | | | Unit: % | | Single-node, master/standby, or cluster DCS Redis instance | | - | | | | | | | - | | | | | Dimension: | | - | | | | | | | - | | | | | dcs_instance_id | | + | | | Unit: % | | | | +----------------------------+----------------------------+----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+---------------+------------------------------------------------------------+------------------------------+ - | connections_usage | Connection Usage | Percentage of the current number of connections to the maximum allowed number of connections | >= 0 | Monitored object: | 1 minute | + | connections_usage | Connection Usage | Percentage of the current number of connections to the maximum allowed number of connections | >= 0 | Single-node, master/standby, or cluster DCS Redis instance | 1 minute | | | | | | | | - | | | Unit: % | | Single-node, master/standby, or cluster DCS Redis instance | | - | | | | | | | - | | | | | Dimension: | | - | | | | | | | - | | | | | dcs_instance_id | | + | | | Unit: % | | | | +----------------------------+----------------------------+----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+---------------+------------------------------------------------------------+------------------------------+ - | Instance Node Status | Instance Node Status | Status of instance nodes. If the status is normal, the value is **0**. If the status is abnormal, the value is **1**. | ``-`` | Monitored object: | 1 minute | - | | | | | | | - | | | | | Single-node, master/standby, or cluster DCS Redis instance | | - | | | | | | | - | | | | | Dimension: | | - | | | | | | | - | | | | | dcs_instance_id | | + | Instance Node Status | Instance Node Status | Status of instance nodes. If the status is normal, the value is **0**. If the status is abnormal, the value is **1**. | ``-`` | Single-node, master/standby, or cluster DCS Redis instance | 1 minute | +----------------------------+----------------------------+----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+---------------+------------------------------------------------------------+------------------------------+ - | command_max_rt | Maximum Latency | Maximum delay from when the node receives commands to when it responds | >= 0 | Monitored object: | 1 minute | + | command_max_rt | Maximum Latency | Maximum delay from when the node receives commands to when it responds | >= 0 | Single-node DCS Redis instance | 1 minute | | | | | | | | - | | | Unit: μs | | Single-node, master/standby, or cluster DCS Redis instance | | - | | | | | | | - | | | | | Dimension: | | - | | | | | | | - | | | | | dcs_instance_id | | + | | | Unit: μs | | | | +----------------------------+----------------------------+----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+---------------+------------------------------------------------------------+------------------------------+ - | command_avg_rt | Average Latency | Average delay from when the node receives commands to when it responds | >= 0 | Monitored object: | 1 minute | + | command_avg_rt | Average Latency | Average delay from when the node receives commands to when it responds | >= 0 | Single-node DCS Redis instance | 1 minute | | | | | | | | - | | | Unit: μs | | Single-node, master/standby, or cluster DCS Redis instance | | - | | | | | | | - | | | | | Dimension: | | - | | | | | | | - | | | | | dcs_instance_id | | + | | | Unit: μs | | | | +----------------------------+----------------------------+----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+---------------+------------------------------------------------------------+------------------------------+ - | cpu_avg_usage | Average CPU Usage | Current average usage of CPU resources | >= 0 | Monitored object: | 1 minute | + | cpu_avg_usage | Average CPU Usage | Current average usage of CPU resources | >= 0 | Single-node or master/standby DCS Redis instance | 1 minute | | | | | | | | - | | | Unit: % | | Single-node, master/standby, or cluster DCS Redis instance | | - | | | | | | | - | | | | | Dimension: | | - | | | | | | | - | | | | | dcs_instance_id | | + | | | Unit: % | | | | +----------------------------+----------------------------+----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+---------------+------------------------------------------------------------+------------------------------+ - | blocked_clients | Blocked Clients | Number of clients suspended by block operations | >= 0 | Monitored object: | 1 minute | - | | | | | | | - | | | | | Single-node, master/standby, or cluster DCS Redis instance | | - | | | | | | | - | | | | | Dimension: | | - | | | | | | | - | | | | | dcs_instance_id | | + | blocked_clients | Blocked Clients | Number of clients suspended by block operations | >= 0 | Single-node, master/standby, or cluster DCS Redis instance | 1 minute | +----------------------------+----------------------------+----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+---------------+------------------------------------------------------------+------------------------------+ - | connected_clients | Connected Clients | Number of connected clients (excluding those from slave nodes) | >= 0 | Monitored object: | 1 minute | - | | | | | | | - | | | | | Single-node, master/standby, or cluster DCS Redis instance | | - | | | | | | | - | | | | | Dimension: | | - | | | | | | | - | | | | | dcs_instance_id | | + | connected_clients | Connected Clients | Number of connected clients (excluding those from slave nodes) | >= 0 | Single-node, master/standby, or cluster DCS Redis instance | 1 minute | +----------------------------+----------------------------+----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+---------------+------------------------------------------------------------+------------------------------+ - | del | DEL | Number of **DEL** commands processed per second | 0-500,000 | Monitored object: | 1 minute | + | del | DEL | Number of **DEL** commands processed per second | 0-500,000 | Single-node, master/standby, or cluster DCS Redis instance | 1 minute | | | | | | | | - | | | Unit: count/s | | Single-node, master/standby, or cluster DCS Redis instance | | - | | | | | | | - | | | | | Dimension: | | - | | | | | | | - | | | | | dcs_instance_id | | + | | | Unit: count/s | | | | +----------------------------+----------------------------+----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+---------------+------------------------------------------------------------+------------------------------+ - | evicted_keys | Evicted Keys | Number of keys that have been evicted and deleted during the monitoring period | >= 0 | Monitored object: | 1 minute | - | | | | | | | - | | | | | Single-node, master/standby, or cluster DCS Redis instance | | - | | | | | | | - | | | | | Dimension: | | - | | | | | | | - | | | | | dcs_instance_id | | + | evicted_keys | Evicted Keys | Number of keys that have been evicted and deleted during the monitoring period | >= 0 | Single-node, master/standby, or cluster DCS Redis instance | 1 minute | +----------------------------+----------------------------+----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+---------------+------------------------------------------------------------+------------------------------+ - | expire | EXPIRE | Number of **EXPIRE** commands processed per second | 0-500,000 | Monitored object: | 1 minute | + | expire | EXPIRE | Number of **EXPIRE** commands processed per second | 0-500,000 | Single-node, master/standby, or cluster DCS Redis instance | 1 minute | | | | | | | | - | | | Unit: count/s | | Single-node, master/standby, or cluster DCS Redis instance | | - | | | | | | | - | | | | | Dimension: | | - | | | | | | | - | | | | | dcs_instance_id | | + | | | Unit: count/s | | | | +----------------------------+----------------------------+----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+---------------+------------------------------------------------------------+------------------------------+ - | expired_keys | Expired Keys | Number of keys that have expired and been deleted during the monitoring period | >= 0 | Monitored object: | 1 minute | - | | | | | | | - | | | | | Single-node, master/standby, or cluster DCS Redis instance | | - | | | | | | | - | | | | | Dimension: | | - | | | | | | | - | | | | | dcs_instance_id | | + | expired_keys | Expired Keys | Number of keys that have expired and been deleted during the monitoring period | >= 0 | Single-node, master/standby, or cluster DCS Redis instance | 1 minute | +----------------------------+----------------------------+----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+---------------+------------------------------------------------------------+------------------------------+ - | get | GET | Number of **GET** commands processed per second | 0-500,000 | Monitored object: | 1 minute | + | get | GET | Number of **GET** commands processed per second | 0-500,000 | Single-node, master/standby, or cluster DCS Redis instance | 1 minute | | | | | | | | - | | | Unit: count/s | | Single-node, master/standby, or cluster DCS Redis instance | | - | | | | | | | - | | | | | Dimension: | | - | | | | | | | - | | | | | dcs_instance_id | | + | | | Unit: count/s | | | | +----------------------------+----------------------------+----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+---------------+------------------------------------------------------------+------------------------------+ - | hdel | HDEL | Number of **HDEL** commands processed per second | 0-500,000 | Monitored object: | 1 minute | + | hdel | HDEL | Number of **HDEL** commands processed per second | 0-500,000 | Single-node, master/standby, or cluster DCS Redis instance | 1 minute | | | | | | | | - | | | Unit: count/s | | Single-node, master/standby, or cluster DCS Redis instance | | - | | | | | | | - | | | | | Dimension: | | - | | | | | | | - | | | | | dcs_instance_id | | + | | | Unit: count/s | | | | +----------------------------+----------------------------+----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+---------------+------------------------------------------------------------+------------------------------+ - | hget | HGET | Number of **HGET** commands processed per second | 0-500,000 | Monitored object: | 1 minute | + | hget | HGET | Number of **HGET** commands processed per second | 0-500,000 | Single-node, master/standby, or cluster DCS Redis instance | 1 minute | | | | | | | | - | | | Unit: count/s | | Single-node, master/standby, or cluster DCS Redis instance | | - | | | | | | | - | | | | | Dimension: | | - | | | | | | | - | | | | | dcs_instance_id | | + | | | Unit: count/s | | | | +----------------------------+----------------------------+----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+---------------+------------------------------------------------------------+------------------------------+ - | hmget | HMGET | Number of **HMGET** commands processed per second | 0-500,000 | Monitored object: | 1 minute | + | hmget | HMGET | Number of **HMGET** commands processed per second | 0-500,000 | Single-node, master/standby, or cluster DCS Redis instance | 1 minute | | | | | | | | - | | | Unit: count/s | | Single-node, master/standby, or cluster DCS Redis instance | | - | | | | | | | - | | | | | Dimension: | | - | | | | | | | - | | | | | dcs_instance_id | | + | | | Unit: count/s | | | | +----------------------------+----------------------------+----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+---------------+------------------------------------------------------------+------------------------------+ - | hmset | HMSET | Number of **HMSET** commands processed per second | 0-500,000 | Monitored object: | 1 minute | + | hmset | HMSET | Number of **HMSET** commands processed per second | 0-500,000 | Single-node, master/standby, or cluster DCS Redis instance | 1 minute | | | | | | | | - | | | Unit: count/s | | Single-node, master/standby, or cluster DCS Redis instance | | - | | | | | | | - | | | | | Dimension: | | - | | | | | | | - | | | | | dcs_instance_id | | + | | | Unit: count/s | | | | +----------------------------+----------------------------+----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+---------------+------------------------------------------------------------+------------------------------+ - | hset | HSET | Number of **HSET** commands processed per second | 0-500,000 | Monitored object: | 1 minute | + | hset | HSET | Number of **HSET** commands processed per second | 0-500,000 | Single-node, master/standby, or cluster DCS Redis instance | 1 minute | | | | | | | | - | | | Unit: count/s | | Single-node, master/standby, or cluster DCS Redis instance | | - | | | | | | | - | | | | | Dimension: | | - | | | | | | | - | | | | | dcs_instance_id | | + | | | Unit: count/s | | | | +----------------------------+----------------------------+----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+---------------+------------------------------------------------------------+------------------------------+ - | instantaneous_input_kbps | Input Flow | Instantaneous input traffic | >= 0 KB/s | Monitored object: | 1 minute | + | instantaneous_input_kbps | Input Flow | Instantaneous input traffic | >= 0 KB/s | Single-node, master/standby, or cluster DCS Redis instance | 1 minute | | | | | | | | - | | | Unit: KB/s | | Single-node, master/standby, or cluster DCS Redis instance | | - | | | | | | | - | | | | | Dimension: | | - | | | | | | | - | | | | | dcs_instance_id | | + | | | Unit: KB/s | | | | +----------------------------+----------------------------+----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+---------------+------------------------------------------------------------+------------------------------+ - | instantaneous_output_kbps | Output Flow | Instantaneous output traffic | >= 0 KB/s | Monitored object: | 1 minute | + | instantaneous_output_kbps | Output Flow | Instantaneous output traffic | >= 0 KB/s | Single-node, master/standby, or cluster DCS Redis instance | 1 minute | | | | | | | | - | | | Unit: KB/s | | Single-node, master/standby, or cluster DCS Redis instance | | - | | | | | | | - | | | | | Dimension: | | - | | | | | | | - | | | | | dcs_instance_id | | + | | | Unit: KB/s | | | | +----------------------------+----------------------------+----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+---------------+------------------------------------------------------------+------------------------------+ - | memory_frag_ratio | Memory Fragmentation Ratio | Ratio between Used Memory RSS and Used Memory | >= 0 | Monitored object: | 1 minute | - | | | | | | | - | | | | | Single-node, master/standby, or cluster DCS Redis instance | | - | | | | | | | - | | | | | Dimension: | | - | | | | | | | - | | | | | dcs_instance_id | | + | memory_frag_ratio | Memory Fragmentation Ratio | Ratio between Used Memory RSS and Used Memory | >= 0 | Single-node, master/standby, or cluster DCS Redis instance | 1 minute | +----------------------------+----------------------------+----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+---------------+------------------------------------------------------------+------------------------------+ - | mget | MGET | Number of **MGET** commands processed per second | 0-500,000 | Monitored object: | 1 minute | + | mget | MGET | Number of **MGET** commands processed per second | 0-500,000 | Single-node, master/standby, or cluster DCS Redis instance | 1 minute | | | | | | | | - | | | Unit: count/s | | Single-node, master/standby, or cluster DCS Redis instance | | - | | | | | | | - | | | | | Dimension: | | - | | | | | | | - | | | | | dcs_instance_id | | + | | | Unit: count/s | | | | +----------------------------+----------------------------+----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+---------------+------------------------------------------------------------+------------------------------+ - | mset | MSET | Number of **MSET** commands processed per second | 0-500,000 | Monitored object: | 1 minute | + | mset | MSET | Number of **MSET** commands processed per second | 0-500,000 | Single-node, master/standby, or cluster DCS Redis instance | 1 minute | | | | | | | | - | | | Unit: count/s | | Single-node, master/standby, or cluster DCS Redis instance | | - | | | | | | | - | | | | | Dimension: | | - | | | | | | | - | | | | | dcs_instance_id | | + | | | Unit: count/s | | | | +----------------------------+----------------------------+----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+---------------+------------------------------------------------------------+------------------------------+ - | pubsub_channels | PubSub Channels | Number of Pub/Sub channels | >= 0 | Monitored object: | 1 minute | - | | | | | | | - | | | | | Single-node, master/standby, or cluster DCS Redis instance | | - | | | | | | | - | | | | | Dimension: | | - | | | | | | | - | | | | | dcs_instance_id | | + | pubsub_channels | PubSub Channels | Number of Pub/Sub channels | >= 0 | Single-node, master/standby, or cluster DCS Redis instance | 1 minute | +----------------------------+----------------------------+----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+---------------+------------------------------------------------------------+------------------------------+ - | pubsub_patterns | PubSub Patterns | Number of Pub/Sub patterns | >= 0 | Monitored object: | 1 minute | - | | | | | | | - | | | | | Single-node, master/standby, or cluster DCS Redis instance | | - | | | | | | | - | | | | | Dimension: | | - | | | | | | | - | | | | | dcs_instance_id | | + | pubsub_patterns | PubSub Patterns | Number of Pub/Sub patterns | >= 0 | Single-node, master/standby, or cluster DCS Redis instance | 1 minute | +----------------------------+----------------------------+----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+---------------+------------------------------------------------------------+------------------------------+ - | set | SET | Number of **SET** commands processed per second | 0-500,000 | Monitored object: | 1 minute | + | set | SET | Number of **SET** commands processed per second | 0-500,000 | Single-node, master/standby, or cluster DCS Redis instance | 1 minute | | | | | | | | - | | | Unit: count/s | | Single-node, master/standby, or cluster DCS Redis instance | | - | | | | | | | - | | | | | Dimension: | | - | | | | | | | - | | | | | dcs_instance_id | | + | | | Unit: count/s | | | | +----------------------------+----------------------------+----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+---------------+------------------------------------------------------------+------------------------------+ - | used_memory_lua | Used Memory Lua | Number of bytes used by the Lua engine | >= 0 | Monitored object: | 1 minute | + | used_memory_lua | Used Memory Lua | Number of bytes used by the Lua engine | >= 0 | Single-node, master/standby, or cluster DCS Redis instance | 1 minute | | | | | | | | - | | | Unit: byte | | Single-node, master/standby, or cluster DCS Redis instance | | - | | | | | | | - | | | | | Dimension: | | - | | | | | | | - | | | | | dcs_instance_id | | + | | | Unit: byte | | | | +----------------------------+----------------------------+----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+---------------+------------------------------------------------------------+------------------------------+ - | used_memory_peak | Used Memory Peak | Peak memory consumed by Redis since the Redis server last started | >= 0 | Monitored object: | 1 minute | + | used_memory_peak | Used Memory Peak | Peak memory consumed by Redis since the Redis server last started | >= 0 | Single-node, master/standby, or cluster DCS Redis instance | 1 minute | | | | | | | | - | | | Unit: byte | | Single-node, master/standby, or cluster DCS Redis instance | | - | | | | | | | - | | | | | Dimension: | | - | | | | | | | - | | | | | dcs_instance_id | | + | | | Unit: byte | | | | +----------------------------+----------------------------+----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+---------------+------------------------------------------------------------+------------------------------+ - | sadd | Sadd | Number of **SADD** commands processed per second | 0-500,000 | Monitored object: | 1 minute | + | sadd | Sadd | Number of **SADD** commands processed per second | 0-500,000 | Single-node, master/standby, or cluster DCS Redis instance | 1 minute | | | | | | | | - | | | Unit: count/s | | Single-node, master/standby, or cluster DCS Redis instance | | - | | | | | | | - | | | | | Dimension: | | - | | | | | | | - | | | | | dcs_instance_id | | + | | | Unit: count/s | | | | +----------------------------+----------------------------+----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+---------------+------------------------------------------------------------+------------------------------+ - | smembers | Smembers | Number of **SMEMBERS** commands processed per second | 0-500,000 | Monitored object: | 1 minute | + | smembers | Smembers | Number of **SMEMBERS** commands processed per second | 0-500,000 | Single-node, master/standby, or cluster DCS Redis instance | 1 minute | | | | | | | | - | | | Unit: count/s | | Single-node, master/standby, or cluster DCS Redis instance | | - | | | | | | | - | | | | | Dimension: | | - | | | | | | | - | | | | | dcs_instance_id | | + | | | Unit: count/s | | | | +----------------------------+----------------------------+----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+---------------+------------------------------------------------------------+------------------------------+ - | rx_controlled | Flow Control Times | Number of flow control times during the monitoring period | >= 0 | Monitored object: | 1 minute | + | rx_controlled | Flow Control Times | Number of flow control times during the monitoring period | >= 0 | Single-node, master/standby, or cluster DCS Redis instance | 1 minute | | | | | | | | - | | | Unit: count | | Redis Cluster instance | | - | | | | | | | - | | | | | Dimension: | | - | | | | | | | - | | | | | dcs_instance_id | | + | | | Unit: count | | | | +----------------------------+----------------------------+----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+---------------+------------------------------------------------------------+------------------------------+ - | bandwidth_usage | Bandwidth Usage | Percentage of the used bandwidth to the maximum bandwidth limit | 0-200% | Monitored object: | 1 minute | - | | | | | | | - | | | | | Redis Cluster instance | | - | | | | | | | - | | | | | Dimension: | | - | | | | | | | - | | | | | dcs_instance_id | | + | bandwidth_usage | Bandwidth Usage | Percentage of the used bandwidth to the maximum bandwidth limit | 0-200% | Single-node, master/standby, or cluster DCS Redis instance | 1 minute | +----------------------------+----------------------------+----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+---------------+------------------------------------------------------------+------------------------------+ - | keyspace_misses | Keyspace Misses | Number of failed lookups of keys in the main dictionary during the monitoring period | >= 0 | Monitored object: | 1 minute | - | | | | | | | - | | | | | Single-node, master/standby, or cluster DCS Redis instance | | - | | | | | | | - | | | | | Dimension: | | - | | | | | | | - | | | | | dcs_instance_id | | + | keyspace_misses | Keyspace Misses | Number of failed lookups of keys in the main dictionary during the monitoring period | >= 0 | Single-node, master/standby, or cluster DCS Redis instance | 1 minute | +----------------------------+----------------------------+----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+---------------+------------------------------------------------------------+------------------------------+ - | used_memory_dataset | Used Memory Dataset | Dataset memory that the Redis server has used | >= 0 | Monitored object: | 1 minute | - | | | | | | | - | | | | | Single-node, master/standby, or cluster DCS Redis instance | | - | | | | | | | - | | | | | Dimension: | | - | | | | | | | - | | | | | dcs_instance_id | | + | used_memory_dataset | Used Memory Dataset | Dataset memory that the Redis server has used | >= 0 | Single-node, master/standby, or cluster DCS Redis instance | 1 minute | +----------------------------+----------------------------+----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+---------------+------------------------------------------------------------+------------------------------+ - | used_memory_dataset_perc | Used Memory Dataset Ratio | Percentage of dataset memory that server has used | 0-100% | Monitored object: | 1 minute | - | | | | | | | - | | | | | Single-node, master/standby, or cluster DCS Redis instance | | - | | | | | | | - | | | | | Dimension: | | - | | | | | | | - | | | | | dcs_instance_id | | + | used_memory_dataset_perc | Used Memory Dataset Ratio | Percentage of dataset memory that server has used | 0-100% | Single-node, master/standby, or cluster DCS Redis instance | 1 minute | +----------------------------+----------------------------+----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+---------------+------------------------------------------------------------+------------------------------+ Node Metrics of DCS Redis Instances @@ -726,571 +326,246 @@ Node Metrics of DCS Redis Instances .. note:: - - The following describes the metrics for cluster DCS instances. For Proxy Cluster DCS Redis 3.0 instances, the monitoring covers Redis Servers and Proxies. For Redis Cluster DCS Redis 4.0 and 5.0 instances, the monitoring only covers Redis Servers. For details, see :ref:`Table 3 ` and :ref:`Table 4 `. + - The following describes the metrics for cluster DCS instances. For Proxy Cluster instances, the monitoring covers Redis Servers and Proxies. For Redis Cluster instances, the monitoring only covers Redis Servers. For details about the monitoring metrics, see :ref:`Table 3 `, :ref:`Table 4 `,. - - The **Monitored Objects and Dimensions** column lists instances and dimensions that support the corresponding metrics. + - The **Monitored Object** column lists instances that support the corresponding metrics. + - :ref:`Dimensions ` lists the metric dimensions. .. _dcs-ug-0326019__table11307163610588: .. table:: **Table 3** Redis Server metrics of DCS instances - +----------------------------+----------------------------+--------------------------------------------------------------------------------------------------------------------------------+---------------+---------------------------------------------------------------+------------------------------+ - | Metric ID | Metric | Description | Value Range | Monitored Object and Dimension | Monitoring Period (Raw Data) | - +============================+============================+================================================================================================================================+===============+===============================================================+==============================+ - | cpu_usage | CPU Usage | The monitored object's maximum CPU usage among multiple sampling values in a monitoring period | 0-100% | Monitored object: | 1 minute | - | | | | | | | - | | | Unit: % | | Redis Server of a cluster DCS Redis 3.0, 4.0, or 5.0 instance | | - | | | | | | | - | | | | | Dimension: | | - | | | | | | | - | | | | | dcs_instance_id | | - | | | | | | | - | | | | | dcs_cluster_redis_node | | - +----------------------------+----------------------------+--------------------------------------------------------------------------------------------------------------------------------+---------------+---------------------------------------------------------------+------------------------------+ - | memory_usage | Memory Usage | Memory consumed by the monitored object | 0-100% | Monitored object: | 1 minute | - | | | | | | | - | | | Unit: % | | Redis Server of a cluster DCS Redis 3.0, 4.0, or 5.0 instance | | - | | | | | | | - | | | | | Dimension: | | - | | | | | | | - | | | | | dcs_cluster_redis_node | | - +----------------------------+----------------------------+--------------------------------------------------------------------------------------------------------------------------------+---------------+---------------------------------------------------------------+------------------------------+ - | connected_clients | Connected Clients | Number of connected clients (excluding those from slave nodes) | >= 0 | Monitored object: | 1 minute | - | | | | | | | - | | | | | Redis Server of a cluster DCS Redis 3.0, 4.0, or 5.0 instance | | - | | | | | | | - | | | | | Dimension: | | - | | | | | | | - | | | | | dcs_instance_id | | - | | | | | | | - | | | | | dcs_cluster_redis_node | | - +----------------------------+----------------------------+--------------------------------------------------------------------------------------------------------------------------------+---------------+---------------------------------------------------------------+------------------------------+ - | client_longest_out_list | Client Longest Output List | Longest output list among current client connections | >= 0 | Monitored object: | 1 minute | - | | | | | | | - | | | | | Redis Server of a cluster DCS Redis 3.0, 4.0, or 5.0 instance | | - | | | | | | | - | | | | | Dimension: | | - | | | | | | | - | | | | | dcs_instance_id | | - | | | | | | | - | | | | | dcs_cluster_redis_node | | - +----------------------------+----------------------------+--------------------------------------------------------------------------------------------------------------------------------+---------------+---------------------------------------------------------------+------------------------------+ - | client_biggest_in_buf | Client Biggest Input Buf | Maximum input data length among current client connections | >= 0 | Monitored object: | 1 minute | - | | | | | | | - | | | Unit: byte | | Redis Server of a cluster DCS Redis 3.0, 4.0, or 5.0 instance | | - | | | | | | | - | | | | | Dimension: | | - | | | | | | | - | | | | | dcs_instance_id | | - | | | | | | | - | | | | | dcs_cluster_redis_node | | - +----------------------------+----------------------------+--------------------------------------------------------------------------------------------------------------------------------+---------------+---------------------------------------------------------------+------------------------------+ - | blocked_clients | Blocked Clients | Number of clients suspended by block operations such as BLPOP, BRPOP, and BRPOPLPUSH | >= 0 | Monitored object: | 1 minute | - | | | | | | | - | | | | | Redis Server of a cluster DCS Redis 3.0, 4.0, or 5.0 instance | | - | | | | | | | - | | | | | Dimension: | | - | | | | | | | - | | | | | dcs_instance_id | | - | | | | | | | - | | | | | dcs_cluster_redis_node | | - +----------------------------+----------------------------+--------------------------------------------------------------------------------------------------------------------------------+---------------+---------------------------------------------------------------+------------------------------+ - | used_memory | Used Memory | Number of bytes used by the Redis server | >= 0 | Monitored object: | 1 minute | - | | | | | | | - | | | Unit: byte | | Redis Server of a cluster DCS Redis 3.0, 4.0, or 5.0 instance | | - | | | | | | | - | | | | | Dimension: | | - | | | | | | | - | | | | | dcs_instance_id | | - | | | | | | | - | | | | | dcs_cluster_redis_node | | - +----------------------------+----------------------------+--------------------------------------------------------------------------------------------------------------------------------+---------------+---------------------------------------------------------------+------------------------------+ - | used_memory_rss | Used Memory RSS | RSS memory that the Redis server has used, which including all stack and heap memory but not swapped-out memory | >= 0 | Monitored object: | 1 minute | - | | | | | | | - | | | Unit: byte | | Redis Server of a cluster DCS Redis 3.0, 4.0, or 5.0 instance | | - | | | | | | | - | | | | | Dimension: | | - | | | | | | | - | | | | | dcs_instance_id | | - | | | | | | | - | | | | | dcs_cluster_redis_node | | - +----------------------------+----------------------------+--------------------------------------------------------------------------------------------------------------------------------+---------------+---------------------------------------------------------------+------------------------------+ - | used_memory_peak | Used Memory Peak | Peak memory consumed by Redis since the Redis server last started | >= 0 | Monitored object: | 1 minute | - | | | | | | | - | | | Unit: byte | | Redis Server of a cluster DCS Redis 3.0, 4.0, or 5.0 instance | | - | | | | | | | - | | | | | Dimension: | | - | | | | | | | - | | | | | dcs_instance_id | | - | | | | | | | - | | | | | dcs_cluster_redis_node | | - +----------------------------+----------------------------+--------------------------------------------------------------------------------------------------------------------------------+---------------+---------------------------------------------------------------+------------------------------+ - | used_memory_lua | Used Memory Lua | Number of bytes used by the Lua engine | >= 0 | Monitored object: | 1 minute | - | | | | | | | - | | | Unit: byte | | Redis Server of a cluster DCS Redis 3.0, 4.0, or 5.0 instance | | - | | | | | | | - | | | | | Dimension: | | - | | | | | | | - | | | | | dcs_instance_id | | - | | | | | | | - | | | | | dcs_cluster_redis_node | | - +----------------------------+----------------------------+--------------------------------------------------------------------------------------------------------------------------------+---------------+---------------------------------------------------------------+------------------------------+ - | memory_frag_ratio | Memory Fragmentation Ratio | Current memory fragmentation, which is the ratio between **used_memory_rss**/**used_memory**. | >= 0 | Monitored object: | 1 minute | - | | | | | | | - | | | | | Redis Server of a cluster DCS Redis 3.0, 4.0, or 5.0 instance | | - | | | | | | | - | | | | | Dimension: | | - | | | | | | | - | | | | | dcs_instance_id | | - | | | | | | | - | | | | | dcs_cluster_redis_node | | - +----------------------------+----------------------------+--------------------------------------------------------------------------------------------------------------------------------+---------------+---------------------------------------------------------------+------------------------------+ - | total_connections_received | New Connections | Number of connections received during the monitoring period | >= 0 | Monitored object: | 1 minute | - | | | | | | | - | | | | | Redis Server of a cluster DCS Redis 3.0, 4.0, or 5.0 instance | | - | | | | | | | - | | | | | Dimension: | | - | | | | | | | - | | | | | dcs_instance_id | | - | | | | | | | - | | | | | dcs_cluster_redis_node | | - +----------------------------+----------------------------+--------------------------------------------------------------------------------------------------------------------------------+---------------+---------------------------------------------------------------+------------------------------+ - | total_commands_processed | Commands Processed | Number of commands processed during the monitoring period | >= 0 | Monitored object: | 1 minute | - | | | | | | | - | | | | | Redis Server of a cluster DCS Redis 3.0, 4.0, or 5.0 instance | | - | | | | | | | - | | | | | Dimension: | | - | | | | | | | - | | | | | dcs_instance_id | | - | | | | | | | - | | | | | dcs_cluster_redis_node | | - +----------------------------+----------------------------+--------------------------------------------------------------------------------------------------------------------------------+---------------+---------------------------------------------------------------+------------------------------+ - | instantaneous_ops | Ops per Second | Number of commands processed per second | >= 0 | Monitored object: | 1 minute | - | | | | | | | - | | | | | Redis Server of a cluster DCS Redis 3.0, 4.0, or 5.0 instance | | - | | | | | | | - | | | | | Dimension: | | - | | | | | | | - | | | | | dcs_instance_id | | - | | | | | | | - | | | | | dcs_cluster_redis_node | | - +----------------------------+----------------------------+--------------------------------------------------------------------------------------------------------------------------------+---------------+---------------------------------------------------------------+------------------------------+ - | total_net_input_bytes | Network Input Bytes | Number of bytes received during the monitoring period | >= 0 | Monitored object: | 1 minute | - | | | | | | | - | | | Unit: byte | | Redis Server of a cluster DCS Redis 3.0, 4.0, or 5.0 instance | | - | | | | | | | - | | | | | Dimension: | | - | | | | | | | - | | | | | dcs_instance_id | | - | | | | | | | - | | | | | dcs_cluster_redis_node | | - +----------------------------+----------------------------+--------------------------------------------------------------------------------------------------------------------------------+---------------+---------------------------------------------------------------+------------------------------+ - | total_net_output_bytes | Network Output Bytes | Number of bytes sent during the monitoring period | >= 0 | Monitored object: | 1 minute | - | | | | | | | - | | | Unit: byte | | Redis Server of a cluster DCS Redis 3.0, 4.0, or 5.0 instance | | - | | | | | | | - | | | | | Dimension: | | - | | | | | | | - | | | | | dcs_instance_id | | - | | | | | | | - | | | | | dcs_cluster_redis_node | | - +----------------------------+----------------------------+--------------------------------------------------------------------------------------------------------------------------------+---------------+---------------------------------------------------------------+------------------------------+ - | instantaneous_input_kbps | Input Flow | Instantaneous input traffic | >= 0 KB/s | Monitored object: | 1 minute | - | | | | | | | - | | | Unit: KB/s | | Redis Server of a cluster DCS Redis 3.0, 4.0, or 5.0 instance | | - | | | | | | | - | | | | | Dimension: | | - | | | | | | | - | | | | | dcs_instance_id | | - | | | | | | | - | | | | | dcs_cluster_redis_node | | - +----------------------------+----------------------------+--------------------------------------------------------------------------------------------------------------------------------+---------------+---------------------------------------------------------------+------------------------------+ - | instantaneous_output_kbps | Output Flow | Instantaneous output traffic | >= 0 KB/s | Monitored object: | 1 minute | - | | | | | | | - | | | Unit: KB/s | | Redis Server of a cluster DCS Redis 3.0, 4.0, or 5.0 instance | | - | | | | | | | - | | | | | Dimension: | | - | | | | | | | - | | | | | dcs_instance_id | | - | | | | | | | - | | | | | dcs_cluster_redis_node | | - +----------------------------+----------------------------+--------------------------------------------------------------------------------------------------------------------------------+---------------+---------------------------------------------------------------+------------------------------+ - | rejected_connections | Rejected Connections | Number of connections that have exceeded maxclients and been rejected during the monitoring period | >= 0 | Monitored object: | 1 minute | - | | | | | | | - | | | | | Redis Server of a cluster DCS Redis 3.0, 4.0, or 5.0 instance | | - | | | | | | | - | | | | | Dimension: | | - | | | | | | | - | | | | | dcs_instance_id | | - | | | | | | | - | | | | | dcs_cluster_redis_node | | - +----------------------------+----------------------------+--------------------------------------------------------------------------------------------------------------------------------+---------------+---------------------------------------------------------------+------------------------------+ - | expired_keys | Expired Keys | Number of keys that have expired and been deleted during the monitoring period | >= 0 | Monitored object: | 1 minute | - | | | | | | | - | | | | | Redis Server of a cluster DCS Redis 3.0, 4.0, or 5.0 instance | | - | | | | | | | - | | | | | Dimension: | | - | | | | | | | - | | | | | dcs_instance_id | | - | | | | | | | - | | | | | dcs_cluster_redis_node | | - +----------------------------+----------------------------+--------------------------------------------------------------------------------------------------------------------------------+---------------+---------------------------------------------------------------+------------------------------+ - | evicted_keys | Evicted Keys | Number of keys that have been evicted and deleted during the monitoring period | >= 0 | Monitored object: | 1 minute | - | | | | | | | - | | | | | Redis Server of a cluster DCS Redis 3.0, 4.0, or 5.0 instance | | - | | | | | | | - | | | | | Dimension: | | - | | | | | | | - | | | | | dcs_instance_id | | - | | | | | | | - | | | | | dcs_cluster_redis_node | | - +----------------------------+----------------------------+--------------------------------------------------------------------------------------------------------------------------------+---------------+---------------------------------------------------------------+------------------------------+ - | pubsub_channels | PubSub Channels | Number of Pub/Sub channels | >= 0 | Monitored object: | 1 minute | - | | | | | | | - | | | | | Redis Server of a cluster DCS Redis 3.0, 4.0, or 5.0 instance | | - | | | | | | | - | | | | | Dimension: | | - | | | | | | | - | | | | | dcs_instance_id | | - | | | | | | | - | | | | | dcs_cluster_redis_node | | - +----------------------------+----------------------------+--------------------------------------------------------------------------------------------------------------------------------+---------------+---------------------------------------------------------------+------------------------------+ - | pubsub_patterns | PubSub Patterns | Number of Pub/Sub patterns | >= 0 | Monitored object: | 1 minute | - | | | | | | | - | | | | | Redis Server of a cluster DCS Redis 3.0, 4.0, or 5.0 instance | | - | | | | | | | - | | | | | Dimension: | | - | | | | | | | - | | | | | dcs_instance_id | | - | | | | | | | - | | | | | dcs_cluster_redis_node | | - +----------------------------+----------------------------+--------------------------------------------------------------------------------------------------------------------------------+---------------+---------------------------------------------------------------+------------------------------+ - | keyspace_hits_perc | Hit Rate | Ratio of the number of Redis cache hits to the number of lookups. Calculation: keyspace_hits/(keyspace_hits + keyspace_misses) | 0-100% | Monitored object: | 1 minute | - | | | | | | | - | | | Unit: % | | Redis Server of a cluster DCS Redis 3.0, 4.0, or 5.0 instance | | - | | | | | | | - | | | | | Dimension: | | - | | | | | | | - | | | | | dcs_instance_id | | - | | | | | | | - | | | | | dcs_cluster_redis_node | | - +----------------------------+----------------------------+--------------------------------------------------------------------------------------------------------------------------------+---------------+---------------------------------------------------------------+------------------------------+ - | command_max_delay | Maximum Command Latency | Maximum latency of commands | >= 0 ms | Monitored object: | 1 minute | - | | | | | | | - | | | Unit: ms | | Redis Server of a cluster DCS Redis 3.0, 4.0, or 5.0 instance | | - | | | | | | | - | | | | | Dimension: | | - | | | | | | | - | | | | | dcs_instance_id | | - | | | | | | | - | | | | | dcs_cluster_redis_node | | - +----------------------------+----------------------------+--------------------------------------------------------------------------------------------------------------------------------+---------------+---------------------------------------------------------------+------------------------------+ - | is_slow_log_exist | Slow Query Logs | Existence of slow query logs in the node | - **1**: yes | Monitored object: | 1 minute | - | | | | - **0**: no | | | - | | | | | Redis Server of a cluster DCS Redis 3.0, 4.0, or 5.0 instance | | - | | | | | | | - | | | | | Dimension: | | - | | | | | | | - | | | | | dcs_instance_id | | - | | | | | | | - | | | | | dcs_cluster_redis_node | | - +----------------------------+----------------------------+--------------------------------------------------------------------------------------------------------------------------------+---------------+---------------------------------------------------------------+------------------------------+ - | keys | Keys | Number of keys in Redis | >= 0 | Monitored object: | 1 minute | - | | | | | | | - | | | | | Redis Server of a cluster DCS Redis 3.0, 4.0, or 5.0 instance | | - | | | | | | | - | | | | | Dimension: | | - | | | | | | | - | | | | | dcs_instance_id | | - | | | | | | | - | | | | | dcs_cluster_redis_node | | - +----------------------------+----------------------------+--------------------------------------------------------------------------------------------------------------------------------+---------------+---------------------------------------------------------------+------------------------------+ - | sadd | Sadd | Number of **SADD** commands processed per second | 0-500,000 | Monitored object: | 1 minute | - | | | | | | | - | | | Unit: count/s | | Redis Server of a cluster DCS Redis 3.0, 4.0, or 5.0 instance | | - | | | | | | | - | | | | | Dimension: | | - | | | | | | | - | | | | | dcs_instance_id | | - | | | | | | | - | | | | | dcs_cluster_redis_node | | - +----------------------------+----------------------------+--------------------------------------------------------------------------------------------------------------------------------+---------------+---------------------------------------------------------------+------------------------------+ - | smembers | Smembers | Number of **SMEMBERS** commands processed per second | 0-500,000 | Monitored object: | 1 minute | - | | | | | | | - | | | Unit: count/s | | Redis Server of a cluster DCS Redis 4.0 or 5.0 instance | | - | | | | | | | - | | | | | Dimension: | | - | | | | | | | - | | | | | dcs_instance_id | | - | | | | | | | - | | | | | dcs_cluster_redis_node | | - +----------------------------+----------------------------+--------------------------------------------------------------------------------------------------------------------------------+---------------+---------------------------------------------------------------+------------------------------+ - | ms_repl_offset | Replication Gap | Data synchronization gap between the master and the replica | ``-`` | Monitored object: | 1 minute | - | | | | | | | - | | | | | Replica of a cluster DCS Redis 4.0 or 5.0 instance | | - | | | | | | | - | | | | | Dimension: | | - | | | | | | | - | | | | | dcs_instance_id | | - | | | | | | | - | | | | | dcs_cluster_redis_node | | - +----------------------------+----------------------------+--------------------------------------------------------------------------------------------------------------------------------+---------------+---------------------------------------------------------------+------------------------------+ - | del | DEL | Number of **DEL** commands processed per second | 0-500,000 | Monitored object: | 1 minute | - | | | | | | | - | | | Unit: count/s | | Redis Server of a cluster DCS Redis 4.0 or 5.0 instance | | - | | | | | | | - | | | | | Dimension: | | - | | | | | | | - | | | | | dcs_instance_id | | - | | | | | | | - | | | | | dcs_cluster_redis_node | | - +----------------------------+----------------------------+--------------------------------------------------------------------------------------------------------------------------------+---------------+---------------------------------------------------------------+------------------------------+ - | expire | EXPIRE | Number of **EXPIRE** commands processed per second | 0-500,000 | Monitored object: | 1 minute | - | | | | | | | - | | | Unit: count/s | | Redis Server of a cluster DCS Redis 4.0 or 5.0 instance | | - | | | | | | | - | | | | | Dimension: | | - | | | | | | | - | | | | | dcs_instance_id | | - | | | | | | | - | | | | | dcs_cluster_redis_node | | - +----------------------------+----------------------------+--------------------------------------------------------------------------------------------------------------------------------+---------------+---------------------------------------------------------------+------------------------------+ - | get | GET | Number of **GET** commands processed per second | 0-500,000 | Monitored object: | 1 minute | - | | | | | | | - | | | Unit: count/s | | Redis Server of a cluster DCS Redis 4.0 or 5.0 instance | | - | | | | | | | - | | | | | Dimension: | | - | | | | | | | - | | | | | dcs_instance_id | | - | | | | | | | - | | | | | dcs_cluster_redis_node | | - +----------------------------+----------------------------+--------------------------------------------------------------------------------------------------------------------------------+---------------+---------------------------------------------------------------+------------------------------+ - | hdel | HDEL | Number of **HDEL** commands processed per second | 0-500,000 | Monitored object: | 1 minute | - | | | | | | | - | | | Unit: count/s | | Redis Server of a cluster DCS Redis 4.0 or 5.0 instance | | - | | | | | | | - | | | | | Dimension: | | - | | | | | | | - | | | | | dcs_instance_id | | - | | | | | | | - | | | | | dcs_cluster_redis_node | | - +----------------------------+----------------------------+--------------------------------------------------------------------------------------------------------------------------------+---------------+---------------------------------------------------------------+------------------------------+ - | hget | HGET | Number of **HGET** commands processed per second | 0-500,000 | Monitored object: | 1 minute | - | | | | | | | - | | | Unit: count/s | | Redis Server of a cluster DCS Redis 4.0 or 5.0 instance | | - | | | | | | | - | | | | | Dimension: | | - | | | | | | | - | | | | | dcs_instance_id | | - | | | | | | | - | | | | | dcs_cluster_redis_node | | - +----------------------------+----------------------------+--------------------------------------------------------------------------------------------------------------------------------+---------------+---------------------------------------------------------------+------------------------------+ - | hmget | HMGET | Number of **HMGET** commands processed per second | 0-500,000 | Monitored object: | 1 minute | - | | | | | | | - | | | Unit: count/s | | Redis Server of a cluster DCS Redis 4.0 or 5.0 instance | | - | | | | | | | - | | | | | Dimension: | | - | | | | | | | - | | | | | dcs_instance_id | | - | | | | | | | - | | | | | dcs_cluster_redis_node | | - +----------------------------+----------------------------+--------------------------------------------------------------------------------------------------------------------------------+---------------+---------------------------------------------------------------+------------------------------+ - | hmset | HMSET | Number of **HMSET** commands processed per second | 0-500,000 | Monitored object: | 1 minute | - | | | | | | | - | | | Unit: count/s | | Redis Server of a cluster DCS Redis 4.0 or 5.0 instance | | - | | | | | | | - | | | | | Dimension: | | - | | | | | | | - | | | | | dcs_instance_id | | - | | | | | | | - | | | | | dcs_cluster_redis_node | | - +----------------------------+----------------------------+--------------------------------------------------------------------------------------------------------------------------------+---------------+---------------------------------------------------------------+------------------------------+ - | hset | HSET | Number of **HSET** commands processed per second | 0-500,000 | Monitored object: | 1 minute | - | | | | | | | - | | | Unit: count/s | | Redis Server of a cluster DCS Redis 4.0 or 5.0 instance | | - | | | | | | | - | | | | | Dimension: | | - | | | | | | | - | | | | | dcs_instance_id | | - | | | | | | | - | | | | | dcs_cluster_redis_node | | - +----------------------------+----------------------------+--------------------------------------------------------------------------------------------------------------------------------+---------------+---------------------------------------------------------------+------------------------------+ - | mget | MGET | Number of **MGET** commands processed per second | 0-500,000 | Monitored object: | 1 minute | - | | | | | | | - | | | Unit: count/s | | Redis Server of a cluster DCS Redis 4.0 or 5.0 instance | | - | | | | | | | - | | | | | Dimension: | | - | | | | | | | - | | | | | dcs_instance_id | | - | | | | | | | - | | | | | dcs_cluster_redis_node | | - +----------------------------+----------------------------+--------------------------------------------------------------------------------------------------------------------------------+---------------+---------------------------------------------------------------+------------------------------+ - | mset | MSET | Number of **MSET** commands processed per second | 0-500,000 | Monitored object: | 1 minute | - | | | | | | | - | | | Unit: count/s | | Redis Server of a cluster DCS Redis 4.0 or 5.0 instance | | - | | | | | | | - | | | | | Dimension: | | - | | | | | | | - | | | | | dcs_instance_id | | - | | | | | | | - | | | | | dcs_cluster_redis_node | | - +----------------------------+----------------------------+--------------------------------------------------------------------------------------------------------------------------------+---------------+---------------------------------------------------------------+------------------------------+ - | set | SET | Number of **SET** commands processed per second | 0-500,000 | Monitored object: | 1 minute | - | | | | | | | - | | | Unit: count/s | | Redis Server of a cluster DCS Redis 4.0 or 5.0 instance | | - | | | | | | | - | | | | | Dimension: | | - | | | | | | | - | | | | | dcs_instance_id | | - | | | | | | | - | | | | | dcs_cluster_redis_node | | - +----------------------------+----------------------------+--------------------------------------------------------------------------------------------------------------------------------+---------------+---------------------------------------------------------------+------------------------------+ - | rx_controlled | Flow Control Times | Number of flow control times during the monitoring period | >= 0 | Monitored object: | 1 minute | - | | | | | | | - | | | Unit: count | | Redis Server of a cluster DCS Redis 4.0 or 5.0 instance | | - | | | | | | | - | | | | | Dimension: | | - | | | | | | | - | | | | | dcs_instance_id | | - | | | | | | | - | | | | | dcs_cluster_redis_node | | - +----------------------------+----------------------------+--------------------------------------------------------------------------------------------------------------------------------+---------------+---------------------------------------------------------------+------------------------------+ - | bandwidth_usage | Bandwidth Usage | Percentage of the used bandwidth to the maximum bandwidth limit | 0-200% | Monitored object: | 1 minute | - | | | | | | | - | | | | | Redis Server of a cluster DCS Redis 4.0 or 5.0 instance | | - | | | | | | | - | | | | | Dimension: | | - | | | | | | | - | | | | | dcs_instance_id | | - | | | | | | | - | | | | | dcs_cluster_redis_node | | - +----------------------------+----------------------------+--------------------------------------------------------------------------------------------------------------------------------+---------------+---------------------------------------------------------------+------------------------------+ + +----------------------------+----------------------------+--------------------------------------------------------------------------------------------------------------------------------+---------------+-----------------------------------------------------------------+------------------------------+ + | Metric ID | Metric | Description | Value Range | Monitored Object | Monitoring Period (Raw Data) | + +============================+============================+================================================================================================================================+===============+=================================================================+==============================+ + | cpu_usage | CPU Usage | The monitored object's maximum CPU usage among multiple sampling values in a monitoring period | 0-100% | Redis Server of a cluster DCS instance | 1 minute | + | | | | | | | + | | | Unit: % | | Redis Server of a master/standby DCS Redis 4.0/5.0/6.0 instance | | + +----------------------------+----------------------------+--------------------------------------------------------------------------------------------------------------------------------+---------------+-----------------------------------------------------------------+------------------------------+ + | memory_usage | Memory Usage | Memory consumed by the monitored object | 0-100% | Redis Server of a cluster DCS instance | 1 minute | + | | | | | | | + | | | Unit: % | | Redis Server of a master/standby DCS Redis 4.0/5.0/6.0 instance | | + +----------------------------+----------------------------+--------------------------------------------------------------------------------------------------------------------------------+---------------+-----------------------------------------------------------------+------------------------------+ + | connected_clients | Connected Clients | Number of connected clients (excluding those from slave nodes) | >= 0 | Redis Server of a cluster DCS instance | 1 minute | + | | | | | | | + | | | | | Redis Server of a master/standby DCS Redis 4.0/5.0/6.0 instance | | + +----------------------------+----------------------------+--------------------------------------------------------------------------------------------------------------------------------+---------------+-----------------------------------------------------------------+------------------------------+ + | client_longest_out_list | Client Longest Output List | Longest output list among current client connections | >= 0 | Redis Server of a cluster DCS instance | 1 minute | + +----------------------------+----------------------------+--------------------------------------------------------------------------------------------------------------------------------+---------------+-----------------------------------------------------------------+------------------------------+ + | client_biggest_in_buf | Client Biggest Input Buf | Maximum input data length among current client connections | >= 0 | Redis Server of a cluster DCS instance | 1 minute | + | | | | | | | + | | | Unit: byte | | | | + +----------------------------+----------------------------+--------------------------------------------------------------------------------------------------------------------------------+---------------+-----------------------------------------------------------------+------------------------------+ + | blocked_clients | Blocked Clients | Number of clients suspended by block operations such as BLPOP, BRPOP, and BRPOPLPUSH | >= 0 | Redis Server of a cluster DCS instance | 1 minute | + | | | | | | | + | | | | | Redis Server of a master/standby DCS Redis 4.0/5.0/6.0 instance | | + +----------------------------+----------------------------+--------------------------------------------------------------------------------------------------------------------------------+---------------+-----------------------------------------------------------------+------------------------------+ + | used_memory | Used Memory | Number of bytes used by the Redis server | >= 0 | Redis Server of a cluster DCS instance | 1 minute | + | | | | | | | + | | | Unit: byte | | Redis Server of a master/standby DCS Redis 4.0/5.0/6.0 instance | | + +----------------------------+----------------------------+--------------------------------------------------------------------------------------------------------------------------------+---------------+-----------------------------------------------------------------+------------------------------+ + | used_memory_rss | Used Memory RSS | RSS memory that the Redis server has used, which including all stack and heap memory but not swapped-out memory | >= 0 | Redis Server of a cluster DCS instance | 1 minute | + | | | | | | | + | | | Unit: byte | | Redis Server of a master/standby DCS Redis 4.0/5.0/6.0 instance | | + +----------------------------+----------------------------+--------------------------------------------------------------------------------------------------------------------------------+---------------+-----------------------------------------------------------------+------------------------------+ + | used_memory_peak | Used Memory Peak | Peak memory consumed by Redis since the Redis server last started | >= 0 | Redis Server of a cluster DCS instance | 1 minute | + | | | | | | | + | | | Unit: byte | | Redis Server of a master/standby DCS Redis 4.0/5.0/6.0 instance | | + +----------------------------+----------------------------+--------------------------------------------------------------------------------------------------------------------------------+---------------+-----------------------------------------------------------------+------------------------------+ + | used_memory_lua | Used Memory Lua | Number of bytes used by the Lua engine | >= 0 | Redis Server of a cluster DCS instance | 1 minute | + | | | | | | | + | | | Unit: byte | | Redis Server of a master/standby DCS Redis 4.0/5.0/6.0 instance | | + +----------------------------+----------------------------+--------------------------------------------------------------------------------------------------------------------------------+---------------+-----------------------------------------------------------------+------------------------------+ + | memory_frag_ratio | Memory Fragmentation Ratio | Current memory fragmentation, which is the ratio between **used_memory_rss**/**used_memory**. | >= 0 | Redis Server of a cluster DCS instance | 1 minute | + | | | | | | | + | | | | | Redis Server of a master/standby DCS Redis 4.0/5.0/6.0 instance | | + +----------------------------+----------------------------+--------------------------------------------------------------------------------------------------------------------------------+---------------+-----------------------------------------------------------------+------------------------------+ + | total_connections_received | New Connections | Number of connections received during the monitoring period | >= 0 | Redis Server of a cluster DCS instance | 1 minute | + | | | | | | | + | | | | | Redis Server of a master/standby DCS Redis 4.0/5.0/6.0 instance | | + +----------------------------+----------------------------+--------------------------------------------------------------------------------------------------------------------------------+---------------+-----------------------------------------------------------------+------------------------------+ + | total_commands_processed | Commands Processed | Number of commands processed during the monitoring period | >= 0 | Redis Server of a cluster DCS instance | 1 minute | + | | | | | | | + | | | | | Redis Server of a master/standby DCS Redis 4.0/5.0 instance | | + +----------------------------+----------------------------+--------------------------------------------------------------------------------------------------------------------------------+---------------+-----------------------------------------------------------------+------------------------------+ + | instantaneous_ops | Ops per Second | Number of commands processed per second | >= 0 | Redis Server of a cluster DCS instance | 1 minute | + | | | | | | | + | | | | | Redis Server of a master/standby DCS Redis 4.0/5.0/6.0 instance | | + +----------------------------+----------------------------+--------------------------------------------------------------------------------------------------------------------------------+---------------+-----------------------------------------------------------------+------------------------------+ + | total_net_input_bytes | Network Input Bytes | Number of bytes received during the monitoring period | >= 0 | Redis Server of a cluster DCS instance | 1 minute | + | | | | | | | + | | | Unit: byte | | Redis Server of a master/standby DCS Redis 4.0/5.0/6.0 instance | | + +----------------------------+----------------------------+--------------------------------------------------------------------------------------------------------------------------------+---------------+-----------------------------------------------------------------+------------------------------+ + | total_net_output_bytes | Network Output Bytes | Number of bytes sent during the monitoring period | >= 0 | Redis Server of a cluster DCS instance | 1 minute | + | | | | | | | + | | | Unit: byte | | Redis Server of a master/standby DCS Redis 4.0/5.0/6.0 instance | | + +----------------------------+----------------------------+--------------------------------------------------------------------------------------------------------------------------------+---------------+-----------------------------------------------------------------+------------------------------+ + | instantaneous_input_kbps | Input Flow | Instantaneous input traffic | >= 0 KB/s | Redis Server of a cluster DCS instance | 1 minute | + | | | | | | | + | | | Unit: KB/s | | Redis Server of a master/standby DCS Redis 4.0/5.0/6.0 instance | | + +----------------------------+----------------------------+--------------------------------------------------------------------------------------------------------------------------------+---------------+-----------------------------------------------------------------+------------------------------+ + | instantaneous_output_kbps | Output Flow | Instantaneous output traffic | >= 0 KB/s | Redis Server of a cluster DCS instance | 1 minute | + | | | | | | | + | | | Unit: KB/s | | Redis Server of a master/standby DCS Redis 4.0/5.0/6.0 instance | | + +----------------------------+----------------------------+--------------------------------------------------------------------------------------------------------------------------------+---------------+-----------------------------------------------------------------+------------------------------+ + | rejected_connections | Rejected Connections | Number of connections that have exceeded maxclients and been rejected during the monitoring period | >= 0 | Redis Server of a cluster DCS instance | 1 minute | + | | | | | | | + | | | | | Redis Server of a master/standby DCS Redis 4.0/5.0/6.0 instance | | + +----------------------------+----------------------------+--------------------------------------------------------------------------------------------------------------------------------+---------------+-----------------------------------------------------------------+------------------------------+ + | expired_keys | Expired Keys | Number of keys that have expired and been deleted during the monitoring period | >= 0 | Redis Server of a cluster DCS instance | 1 minute | + | | | | | | | + | | | | | Redis Server of a master/standby DCS Redis 4.0/5.0/6.0 instance | | + +----------------------------+----------------------------+--------------------------------------------------------------------------------------------------------------------------------+---------------+-----------------------------------------------------------------+------------------------------+ + | evicted_keys | Evicted Keys | Number of keys that have been evicted and deleted during the monitoring period | >= 0 | Redis Server of a cluster DCS instance | 1 minute | + | | | | | | | + | | | | | Redis Server of a master/standby DCS Redis 4.0/5.0/6.0 instance | | + +----------------------------+----------------------------+--------------------------------------------------------------------------------------------------------------------------------+---------------+-----------------------------------------------------------------+------------------------------+ + | pubsub_channels | PubSub Channels | Number of Pub/Sub channels | >= 0 | Redis Server of a cluster DCS instance | 1 minute | + | | | | | | | + | | | | | Redis Server of a master/standby DCS Redis 4.0/5.0/6.0 instance | | + +----------------------------+----------------------------+--------------------------------------------------------------------------------------------------------------------------------+---------------+-----------------------------------------------------------------+------------------------------+ + | pubsub_patterns | PubSub Patterns | Number of Pub/Sub patterns | >= 0 | Redis Server of a cluster DCS instance | 1 minute | + | | | | | | | + | | | | | Redis Server of a master/standby DCS Redis 4.0/5.0/6.0 instance | | + +----------------------------+----------------------------+--------------------------------------------------------------------------------------------------------------------------------+---------------+-----------------------------------------------------------------+------------------------------+ + | keyspace_hits_perc | Hit Rate | Ratio of the number of Redis cache hits to the number of lookups. Calculation: keyspace_hits/(keyspace_hits + keyspace_misses) | 0-100% | Redis Server of a cluster DCS instance | 1 minute | + | | | | | | | + | | | Unit: % | | Redis Server of a master/standby DCS Redis 4.0/5.0/6.0 instance | | + +----------------------------+----------------------------+--------------------------------------------------------------------------------------------------------------------------------+---------------+-----------------------------------------------------------------+------------------------------+ + | command_max_delay | Maximum Command Latency | Maximum latency of commands | >= 0 ms | Redis Server of a cluster DCS instance | 1 minute | + | | | | | | | + | | | Unit: ms | | Redis Server of a master/standby DCS Redis 4.0/5.0/6.0 instance | | + +----------------------------+----------------------------+--------------------------------------------------------------------------------------------------------------------------------+---------------+-----------------------------------------------------------------+------------------------------+ + | is_slow_log_exist | Slow Query Logs | Existence of slow query logs in the node | - **1**: yes | Redis Server of a cluster DCS instance | 1 minute | + | | | | - **0**: no | | | + | | | | | Redis Server of a master/standby DCS Redis 4.0/5.0/6.0 instance | | + +----------------------------+----------------------------+--------------------------------------------------------------------------------------------------------------------------------+---------------+-----------------------------------------------------------------+------------------------------+ + | keys | Keys | Number of keys in Redis | >= 0 | Redis Server of a cluster DCS instance | 1 minute | + | | | | | | | + | | | | | Redis Server of a master/standby DCS Redis 4.0/5.0/6.0 instance | | + +----------------------------+----------------------------+--------------------------------------------------------------------------------------------------------------------------------+---------------+-----------------------------------------------------------------+------------------------------+ + | sadd | Sadd | Number of **SADD** commands processed per second | 0-500,000 | Redis Server of a cluster DCS instance | 1 minute | + | | | | | | | + | | | Unit: count/s | | Redis Server of a master/standby DCS Redis 4.0/5.0/6.0 instance | | + +----------------------------+----------------------------+--------------------------------------------------------------------------------------------------------------------------------+---------------+-----------------------------------------------------------------+------------------------------+ + | smembers | Smembers | Number of **SMEMBERS** commands processed per second | 0-500,000 | Redis Server of a cluster DCS instance | 1 minute | + | | | | | | | + | | | Unit: count/s | | Redis Server of a master/standby DCS Redis 4.0/5.0/6.0 instance | | + +----------------------------+----------------------------+--------------------------------------------------------------------------------------------------------------------------------+---------------+-----------------------------------------------------------------+------------------------------+ + | ms_repl_offset | Replication Gap | Data synchronization gap between the master and the replica | ``-`` | Replica of a cluster DCS Redis 4.0 or 5.0 instance | 1 minute | + +----------------------------+----------------------------+--------------------------------------------------------------------------------------------------------------------------------+---------------+-----------------------------------------------------------------+------------------------------+ + | del | DEL | Number of **DEL** commands processed per second | 0-500,000 | Redis Server of a cluster DCS instance | 1 minute | + | | | | | | | + | | | Unit: count/s | | Redis Server of a master/standby DCS Redis 4.0/5.0/6.0 instance | | + +----------------------------+----------------------------+--------------------------------------------------------------------------------------------------------------------------------+---------------+-----------------------------------------------------------------+------------------------------+ + | expire | EXPIRE | Number of **EXPIRE** commands processed per second | 0-500,000 | Redis Server of a cluster DCS instance | 1 minute | + | | | | | | | + | | | Unit: count/s | | Redis Server of a master/standby DCS Redis 4.0/5.0/6.0 instance | | + +----------------------------+----------------------------+--------------------------------------------------------------------------------------------------------------------------------+---------------+-----------------------------------------------------------------+------------------------------+ + | get | GET | Number of **GET** commands processed per second | 0-500,000 | Redis Server of a cluster DCS instance | 1 minute | + | | | | | | | + | | | Unit: count/s | | Redis Server of a master/standby DCS Redis 4.0/5.0/6.0 instance | | + +----------------------------+----------------------------+--------------------------------------------------------------------------------------------------------------------------------+---------------+-----------------------------------------------------------------+------------------------------+ + | hdel | HDEL | Number of **HDEL** commands processed per second | 0-500,000 | Redis Server of a cluster DCS instance | 1 minute | + | | | | | | | + | | | Unit: count/s | | Redis Server of a master/standby DCS Redis 4.0/5.0/6.0 instance | | + +----------------------------+----------------------------+--------------------------------------------------------------------------------------------------------------------------------+---------------+-----------------------------------------------------------------+------------------------------+ + | hget | HGET | Number of **HGET** commands processed per second | 0-500,000 | Redis Server of a cluster DCS instance | 1 minute | + | | | | | | | + | | | Unit: count/s | | Redis Server of a master/standby DCS Redis 4.0/5.0/6.0 instance | | + +----------------------------+----------------------------+--------------------------------------------------------------------------------------------------------------------------------+---------------+-----------------------------------------------------------------+------------------------------+ + | hmget | HMGET | Number of **HMGET** commands processed per second | 0-500,000 | Redis Server of a cluster DCS instance | 1 minute | + | | | | | | | + | | | Unit: count/s | | Redis Server of a master/standby DCS Redis 4.0/5.0/6.0 instance | | + +----------------------------+----------------------------+--------------------------------------------------------------------------------------------------------------------------------+---------------+-----------------------------------------------------------------+------------------------------+ + | hmset | HMSET | Number of **HMSET** commands processed per second | 0-500,000 | Redis Server of a cluster DCS instance | 1 minute | + | | | | | | | + | | | Unit: count/s | | Redis Server of a master/standby DCS Redis 4.0/5.0/6.0 instance | | + +----------------------------+----------------------------+--------------------------------------------------------------------------------------------------------------------------------+---------------+-----------------------------------------------------------------+------------------------------+ + | hset | HSET | Number of **HSET** commands processed per second | 0-500,000 | Redis Server of a cluster DCS instance | 1 minute | + | | | | | | | + | | | Unit: count/s | | Redis Server of a master/standby DCS Redis 4.0/5.0/6.0 instance | | + +----------------------------+----------------------------+--------------------------------------------------------------------------------------------------------------------------------+---------------+-----------------------------------------------------------------+------------------------------+ + | mget | MGET | Number of **MGET** commands processed per second | 0-500,000 | Redis Server of a cluster DCS instance | 1 minute | + | | | | | | | + | | | Unit: count/s | | Redis Server of a master/standby DCS Redis 4.0/5.0/6.0 instance | | + +----------------------------+----------------------------+--------------------------------------------------------------------------------------------------------------------------------+---------------+-----------------------------------------------------------------+------------------------------+ + | mset | MSET | Number of **MSET** commands processed per second | 0-500,000 | Redis Server of a cluster DCS instance | 1 minute | + | | | | | | | + | | | Unit: count/s | | Redis Server of a master/standby DCS Redis 4.0/5.0/6.0 instance | | + +----------------------------+----------------------------+--------------------------------------------------------------------------------------------------------------------------------+---------------+-----------------------------------------------------------------+------------------------------+ + | set | SET | Number of **SET** commands processed per second | 0-500,000 | Redis Server of a cluster DCS instance | 1 minute | + | | | | | | | + | | | Unit: count/s | | Redis Server of a master/standby DCS Redis 4.0/5.0/6.0 instance | | + +----------------------------+----------------------------+--------------------------------------------------------------------------------------------------------------------------------+---------------+-----------------------------------------------------------------+------------------------------+ + | rx_controlled | Flow Control Times | Number of flow control times during the monitoring period | >= 0 | Redis Server of a cluster DCS instance | 1 minute | + | | | | | | | + | | | Unit: count | | Redis Server of a master/standby DCS Redis 4.0/5.0/6.0 instance | | + +----------------------------+----------------------------+--------------------------------------------------------------------------------------------------------------------------------+---------------+-----------------------------------------------------------------+------------------------------+ + | bandwidth_usage | Bandwidth Usage | Percentage of the used bandwidth to the maximum bandwidth limit | 0-200% | Redis Server of a cluster DCS instance | 1 minute | + | | | | | | | + | | | | | Redis Server of a master/standby DCS Redis 4.0/5.0/6.0 instance | | + +----------------------------+----------------------------+--------------------------------------------------------------------------------------------------------------------------------+---------------+-----------------------------------------------------------------+------------------------------+ .. _dcs-ug-0326019__en-us_topic_0148195272_table107134417017: -.. table:: **Table 4** Proxy metrics +.. table:: **Table 4** Proxy metrics of Proxy Cluster DCS Redis 3.0 instances +---------------------+---------------------------------------+-----------------------------------------------------------------------------------------------------+--------------+-------------------------------------------------+------------------------------+ | Metric ID | Metric | Description | Value Range | Monitored Object and Dimension | Monitoring Period (Raw Data) | +=====================+=======================================+=====================================================================================================+==============+=================================================+==============================+ - | cpu_usage | CPU Usage | The monitored object's maximum CPU usage among multiple sampling values in a monitoring period | 0-100% | Monitored object: | 1 minute | + | cpu_usage | CPU Usage | The monitored object's maximum CPU usage among multiple sampling values in a monitoring period | 0-100% | Proxy in a Proxy Cluster DCS Redis 3.0 instance | 1 minute | | | | | | | | - | | | Unit: % | | Proxy in a Proxy Cluster DCS Redis 3.0 instance | | - | | | | | | | - | | | | | Dimension: | | - | | | | | | | - | | | | | dcs_instance_id | | - | | | | | | | - | | | | | dcs_cluster_proxy_node | | + | | | Unit: % | | | | +---------------------+---------------------------------------+-----------------------------------------------------------------------------------------------------+--------------+-------------------------------------------------+------------------------------+ - | memory_usage | Memory Usage | Memory consumed by the monitored object | 0-100% | Monitored object: | 1 minute | + | memory_usage | Memory Usage | Memory consumed by the monitored object | 0-100% | Proxy in a Proxy Cluster DCS Redis 3.0 instance | 1 minute | | | | | | | | - | | | Unit: % | | Proxy in a Proxy Cluster DCS Redis 3.0 instance | | - | | | | | | | - | | | | | Dimension: | | - | | | | | | | - | | | | | dcs_instance_id | | - | | | | | | | - | | | | | dcs_cluster_proxy_node | | + | | | Unit: % | | | | +---------------------+---------------------------------------+-----------------------------------------------------------------------------------------------------+--------------+-------------------------------------------------+------------------------------+ - | p_connected_clients | Connected Clients | Number of connected clients | >= 0 | Monitored object: | 1 minute | - | | | | | | | - | | | | | Proxy in a Proxy Cluster DCS Redis 3.0 instance | | - | | | | | | | - | | | | | Dimension: | | - | | | | | | | - | | | | | dcs_instance_id | | - | | | | | | | - | | | | | dcs_cluster_proxy_node | | + | p_connected_clients | Connected Clients | Number of connected clients | >= 0 | Proxy in a Proxy Cluster DCS Redis 3.0 instance | 1 minute | +---------------------+---------------------------------------+-----------------------------------------------------------------------------------------------------+--------------+-------------------------------------------------+------------------------------+ - | max_rxpck_per_sec | Max. NIC Data Packet Receive Rate | Maximum number of data packets received by the proxy NIC per second during the monitoring period | 0-10,000,000 | Monitored object: | 1 minute | + | max_rxpck_per_sec | Max. NIC Data Packet Receive Rate | Maximum number of data packets received by the proxy NIC per second during the monitoring period | 0-10,000,000 | Proxy in a Proxy Cluster DCS Redis 3.0 instance | 1 minute | | | | | | | | - | | | Unit: packages/second | | Proxy in a Proxy Cluster DCS Redis 3.0 instance | | - | | | | | | | - | | | | | Dimension: | | - | | | | | | | - | | | | | dcs_instance_id | | - | | | | | | | - | | | | | dcs_cluster_proxy_node | | + | | | Unit: packages/second | | | | +---------------------+---------------------------------------+-----------------------------------------------------------------------------------------------------+--------------+-------------------------------------------------+------------------------------+ - | max_txpck_per_sec | Max. NIC Data Packet Transmit Rate | Maximum number of data packets transmitted by the proxy NIC per second during the monitoring period | 0-10,000,000 | Monitored object: | 1 minute | + | max_txpck_per_sec | Max. NIC Data Packet Transmit Rate | Maximum number of data packets transmitted by the proxy NIC per second during the monitoring period | 0-10,000,000 | Proxy in a Proxy Cluster DCS Redis 3.0 instance | 1 minute | | | | | | | | - | | | Unit: packages/second | | Proxy in a Proxy Cluster DCS Redis 3.0 instance | | - | | | | | | | - | | | | | Dimension: | | - | | | | | | | - | | | | | dcs_instance_id | | - | | | | | | | - | | | | | dcs_cluster_proxy_node | | + | | | Unit: packages/second | | | | +---------------------+---------------------------------------+-----------------------------------------------------------------------------------------------------+--------------+-------------------------------------------------+------------------------------+ - | max_rxkB_per_sec | Maximum Inbound Bandwidth | Largest volume of data received by the proxy NIC per second | >= 0 KB/s | Monitored object: | 1 minute | + | max_rxkB_per_sec | Maximum Inbound Bandwidth | Largest volume of data received by the proxy NIC per second | >= 0 KB/s | Proxy in a Proxy Cluster DCS Redis 3.0 instance | 1 minute | | | | | | | | - | | | Unit: KB/s | | Proxy in a Proxy Cluster DCS Redis 3.0 instance | | - | | | | | | | - | | | | | Dimension: | | - | | | | | | | - | | | | | dcs_instance_id | | - | | | | | | | - | | | | | dcs_cluster_proxy_node | | + | | | Unit: KB/s | | | | +---------------------+---------------------------------------+-----------------------------------------------------------------------------------------------------+--------------+-------------------------------------------------+------------------------------+ - | max_txkB_per_sec | Maximum Outbound Bandwidth | Largest volume of data transmitted by the proxy NIC per second | >= 0 KB/s | Monitored object: | 1 minute | + | max_txkB_per_sec | Maximum Outbound Bandwidth | Largest volume of data transmitted by the proxy NIC per second | >= 0 KB/s | Proxy in a Proxy Cluster DCS Redis 3.0 instance | 1 minute | | | | | | | | - | | | Unit: KB/s | | Proxy in a Proxy Cluster DCS Redis 3.0 instance | | - | | | | | | | - | | | | | Dimension: | | - | | | | | | | - | | | | | dcs_instance_id | | - | | | | | | | - | | | | | dcs_cluster_proxy_node | | + | | | Unit: KB/s | | | | +---------------------+---------------------------------------+-----------------------------------------------------------------------------------------------------+--------------+-------------------------------------------------+------------------------------+ - | avg_rxpck_per_sec | Average NIC Data Packet Receive Rate | Average number of data packets received by the proxy NIC per second during the monitoring period | 0-10,000,000 | Monitored object: | 1 minute | + | avg_rxpck_per_sec | Average NIC Data Packet Receive Rate | Average number of data packets received by the proxy NIC per second during the monitoring period | 0-10,000,000 | Proxy in a Proxy Cluster DCS Redis 3.0 instance | 1 minute | | | | | | | | - | | | Unit: packages/second | | Proxy in a Proxy Cluster DCS Redis 3.0 instance | | - | | | | | | | - | | | | | Dimension: | | - | | | | | | | - | | | | | dcs_instance_id | | - | | | | | | | - | | | | | dcs_cluster_proxy_node | | + | | | Unit: packages/second | | | | +---------------------+---------------------------------------+-----------------------------------------------------------------------------------------------------+--------------+-------------------------------------------------+------------------------------+ - | avg_txpck_per_sec | Average NIC Data Packet Transmit Rate | Average number of data packets transmitted by the proxy NIC per second during the monitoring period | 0-10,000,000 | Monitored object: | 1 minute | + | avg_txpck_per_sec | Average NIC Data Packet Transmit Rate | Average number of data packets transmitted by the proxy NIC per second during the monitoring period | 0-10,000,000 | Proxy in a Proxy Cluster DCS Redis 3.0 instance | 1 minute | | | | | | | | - | | | Unit: packages/second | | Proxy in a Proxy Cluster DCS Redis 3.0 instance | | - | | | | | | | - | | | | | Dimension: | | - | | | | | | | - | | | | | dcs_instance_id | | - | | | | | | | - | | | | | dcs_cluster_proxy_node | | + | | | Unit: packages/second | | | | +---------------------+---------------------------------------+-----------------------------------------------------------------------------------------------------+--------------+-------------------------------------------------+------------------------------+ - | avg_rxkB_per_sec | Average Inbound Bandwidth | Average volume of data received by the proxy NIC per second | >= 0 KB/s | Monitored object: | 1 minute | + | avg_rxkB_per_sec | Average Inbound Bandwidth | Average volume of data received by the proxy NIC per second | >= 0 KB/s | Proxy in a Proxy Cluster DCS Redis 3.0 instance | 1 minute | | | | | | | | - | | | Unit: KB/s | | Proxy in a Proxy Cluster DCS Redis 3.0 instance | | - | | | | | | | - | | | | | Dimension: | | - | | | | | | | - | | | | | dcs_instance_id | | - | | | | | | | - | | | | | dcs_cluster_proxy_node | | + | | | Unit: KB/s | | | | +---------------------+---------------------------------------+-----------------------------------------------------------------------------------------------------+--------------+-------------------------------------------------+------------------------------+ - | avg_txkB_per_sec | Average Outbound Bandwidth | Average volume of data transmitted by the proxy NIC per second | >= 0 KB/s | Monitored object: | 1 minute | + | avg_txkB_per_sec | Average Outbound Bandwidth | Average volume of data transmitted by the proxy NIC per second | >= 0 KB/s | Proxy in a Proxy Cluster DCS Redis 3.0 instance | 1 minute | | | | | | | | - | | | Unit: KB/s | | Proxy in a Proxy Cluster DCS Redis 3.0 instance | | - | | | | | | | - | | | | | Dimension: | | - | | | | | | | - | | | | | dcs_instance_id | | - | | | | | | | - | | | | | dcs_cluster_proxy_node | | + | | | Unit: KB/s | | | | +---------------------+---------------------------------------+-----------------------------------------------------------------------------------------------------+--------------+-------------------------------------------------+------------------------------+ +.. _dcs-ug-0326019__en-us_topic_0148195272_section10507421184117: + Dimensions ---------- -====================== ================== +====================== =============================================== Key Value -====================== ================== +====================== =============================================== dcs_instance_id DCS Redis instance dcs_cluster_redis_node Redis Server -dcs_cluster_proxy_node Proxy -====================== ================== +dcs_cluster_proxy_node Proxy in a Proxy Cluster DCS Redis 3.0 instance +====================== =============================================== diff --git a/umn/source/operation_guide/backing_up_and_restoring_dcs_instances/manually_backing_up_a_dcs_instance.rst b/umn/source/operation_guide/backing_up_and_restoring_dcs_instances/manually_backing_up_a_dcs_instance.rst index cfe7ee2..7655549 100644 --- a/umn/source/operation_guide/backing_up_and_restoring_dcs_instances/manually_backing_up_a_dcs_instance.rst +++ b/umn/source/operation_guide/backing_up_and_restoring_dcs_instances/manually_backing_up_a_dcs_instance.rst @@ -31,7 +31,7 @@ Procedure #. Select a backup file format. - Only DCS Redis 4.0 and 5.0 instances support backup file format selection. + Only DCS Redis 4.0 and later instances support backup file format selection. #. In the **Create Backup** dialog box, click **OK**. diff --git a/umn/source/operation_guide/backing_up_and_restoring_dcs_instances/overview.rst b/umn/source/operation_guide/backing_up_and_restoring_dcs_instances/overview.rst index dec4090..69d9283 100644 --- a/umn/source/operation_guide/backing_up_and_restoring_dcs_instances/overview.rst +++ b/umn/source/operation_guide/backing_up_and_restoring_dcs_instances/overview.rst @@ -60,7 +60,7 @@ Additional Information About Data Backup It is advisable to back up instance data during off-peak periods. -- Storage and pricing of backup files +- Storage of backup files Backup files are stored to OBS. diff --git a/umn/source/operation_guide/managing_dcs_instances/cache_analysis.rst b/umn/source/operation_guide/managing_dcs_instances/cache_analysis.rst index 48c2912..2533c14 100644 --- a/umn/source/operation_guide/managing_dcs_instances/cache_analysis.rst +++ b/umn/source/operation_guide/managing_dcs_instances/cache_analysis.rst @@ -17,7 +17,7 @@ By performing big key analysis and hot key analysis, you will have a picture of **Notes on hot key analysis:** -- Only DCS Redis 4.0 and 5.0 instances support hot key analysis, and the **maxmemory-policy** parameter of the instances must be set to **allkeys-lfu** or **volatile-lfu**. +- Only DCS Redis 4.0/5.0/6.0 instances support hot key analysis, and the **maxmemory-policy** parameter of the instances must be set to **allkeys-lfu** or **volatile-lfu**. - During hot key analysis, all keys will be traversed. The larger the number of keys, the longer the analysis takes. - Perform hot key analysis shortly after peak hours to ensure the accuracy of the analysis results. - The hot key analysis is performed on the master node of each instance and will reduce the instance access performance by up to 10%. @@ -38,7 +38,7 @@ Big Key Analysis Procedure #. Click the name of a DCS Redis instance. -#. Click the **Cache Analysis** tab. +#. Choose **Cache Analysis** . #. On the **Big Key Analysis** tab page, manually perform big key analysis or schedule daily automatic analysis. @@ -61,13 +61,13 @@ Hot Key Analysis Procedure #. Click the name of a DCS Redis instance. -#. Click the **Cache Analysis** tab. +#. Choose **Cache Analysis** . #. On the **Hot Key Analysis** tab page, manually perform hot key analysis or schedule daily automatic analysis. .. note:: - The default value of the **maxmemory-policy** parameter of a Redis 4.0 or 5.0 instance is **noeviction**. To perform hot key analysis, set this parameter to **allkeys-lfu** or **volatile-lfu**. If this parameter has already been set to **allkeys-lfu** or **volatile-lfu**, perform hot key analysis right away. + If hot key analysis cannot be performed, set **maxmemory-policy** to **allkeys-lfu** or **volatile-lfu**. If this parameter has already been set to **allkeys-lfu** or **volatile-lfu**, perform hot key analysis right away. #. After an analysis task completes, click **View** to view the analysis results. diff --git a/umn/source/operation_guide/managing_dcs_instances/configuring_ssl.rst b/umn/source/operation_guide/managing_dcs_instances/configuring_ssl.rst new file mode 100644 index 0000000..5d6104a --- /dev/null +++ b/umn/source/operation_guide/managing_dcs_instances/configuring_ssl.rst @@ -0,0 +1,30 @@ +:original_name: dcs-ug-023129.html + +.. _dcs-ug-023129: + +Configuring SSL +=============== + +DCS Redis 6.0 instances support SSL encryption to ensure data transmission security. This function is not available for other instance versions. + +Procedure +--------- + +#. Log in to the DCS console. +#. Click |image1| in the upper left corner of the management console and select the region where your instance is located. +#. In the navigation pane, choose **Cache Manager**. +#. On the **Cache Manager** page, click a DCS instance. +#. In the navigation pane, choose **SSL**. +#. Click |image2| next to **SSL Certificate** to enable or disable SSL. + + .. important:: + + - This will restart the instance and disconnect it for a few seconds. Wait until off-peak hours and ensure that your application can re-connect. + - The restart cannot be undone. For single-node DCS instances and other instances where AOF persistence is disabled (**appendonly** is set to **no**), data will be cleared and ongoing backup tasks will be stopped. Exercise caution when performing this operation. + +#. Click **Download Certificate** to download the SSL certificate. +#. Decompress the SSL certificate and upload the decompressed **ca.crt** file to the server where the Redis client is located. +#. Add the path of the **ca.crt** file to the command for connecting to the instance. If you use redis-cli to connect to an instance, refer to :ref:`Accessing a DCS Redis Instance Through redis-cli `. + +.. |image1| image:: /_static/images/en-us_image_0148195246.png +.. |image2| image:: /_static/images/en-us_image_0000001505063901.png diff --git a/umn/source/operation_guide/managing_dcs_instances/index.rst b/umn/source/operation_guide/managing_dcs_instances/index.rst index 0818e74..bf7713c 100644 --- a/umn/source/operation_guide/managing_dcs_instances/index.rst +++ b/umn/source/operation_guide/managing_dcs_instances/index.rst @@ -16,6 +16,7 @@ Managing DCS Instances - :ref:`Managing IP Address Whitelist ` - :ref:`Viewing Redis Slow Logs ` - :ref:`Viewing Redis Run Logs ` +- :ref:`Configuring SSL ` .. toctree:: :maxdepth: 1 @@ -32,3 +33,4 @@ Managing DCS Instances managing_ip_address_whitelist viewing_redis_slow_logs viewing_redis_run_logs + configuring_ssl diff --git a/umn/source/operation_guide/managing_dcs_instances/managing_ip_address_whitelist.rst b/umn/source/operation_guide/managing_dcs_instances/managing_ip_address_whitelist.rst index fd88a7c..8c83385 100644 --- a/umn/source/operation_guide/managing_dcs_instances/managing_ip_address_whitelist.rst +++ b/umn/source/operation_guide/managing_dcs_instances/managing_ip_address_whitelist.rst @@ -7,10 +7,10 @@ Managing IP Address Whitelist DCS helps you control access to your DCS instances in the following ways, depending on the deployment mode: -- To control access to Redis 3.0 instances, you can use security groups. Whitelists are not supported. For details about how to configure a security group, see :ref:`Security Group Configurations `. -- To control access to Redis 4.0 and 5.0 instances, you can use whitelists. Security groups are not supported. +- To control access to DCS Redis 3.0 instances, you can use security groups. Whitelists are not supported. For details about how to configure a security group, see :ref:`Security Group Configurations `. +- To control access to DCS Redis 4.0/5.0/6.0 instances, you can use whitelists. Security groups are not supported. -The following describes how to manage whitelists of a Redis 4.0 or 5.0 instance to allow access only from whitelisted IP addresses. If no whitelists are added for the instance or the whitelist function is disabled, all IP addresses that can communicate with the VPC can access the instance. +The following describes how to manage whitelists of a Redis 4.0/5.0/6.0 instance to allow access only from whitelisted IP addresses. If no whitelists are added for the instance or the whitelist function is disabled, all IP addresses that can communicate with the VPC can access the instance. Creating a Whitelist Group -------------------------- diff --git a/umn/source/operation_guide/managing_dcs_instances/managing_shards_and_replicas.rst b/umn/source/operation_guide/managing_dcs_instances/managing_shards_and_replicas.rst index 54394a6..39e49f2 100644 --- a/umn/source/operation_guide/managing_dcs_instances/managing_shards_and_replicas.rst +++ b/umn/source/operation_guide/managing_dcs_instances/managing_shards_and_replicas.rst @@ -5,7 +5,7 @@ Managing Shards and Replicas ============================ -This section describes how to query the shards and replicas of a DCS Redis 4.0 or 5.0 instance and how to manually promote a replica to master. +This section describes how to query the shards and replicas of a DCS Redis 4.0/5.0/6.0 instance and how to manually promote a replica to master. Currently, **this function is supported only by Redis Cluster DCS Redis 4.0 or 5.0 instances.** @@ -32,9 +32,10 @@ Promoting a Replica to Master **Figure 1** Lists of shards and replicas -7. Click **Promote to Master** in the row containing another replica which is in the "Replica" role. +7. For a cluster instance, you can promote a replica in a shard to be master. -8. Click **Yes**. + a. Click **Promote to Master** in the row containing another replica which is in the "Replica" role. + b. Click **Yes**. .. |image1| image:: /_static/images/en-us_image_0000001241411631.png .. |image2| image:: /_static/images/en-us_image_0000001241691605.png diff --git a/umn/source/operation_guide/managing_dcs_instances/modifying_configuration_parameters.rst b/umn/source/operation_guide/managing_dcs_instances/modifying_configuration_parameters.rst index 187e717..fcfcdba 100644 --- a/umn/source/operation_guide/managing_dcs_instances/modifying_configuration_parameters.rst +++ b/umn/source/operation_guide/managing_dcs_instances/modifying_configuration_parameters.rst @@ -40,6 +40,8 @@ Procedure | Parameter | Description | Value Range | Default Value | +===============================================+=================================================================================================================================================================================================================================================================================================================================+==================================================+==================================================+ | timeout | The maximum amount of time (in seconds) a connection between a client and the DCS instance can be allowed to remain idle before the connection is terminated. A setting of **0** means that this function is disabled. | 0-7200 seconds | 0 | + | | | | | + | | Proxy Cluster instances do not have this parameter. | | | +-----------------------------------------------+---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+--------------------------------------------------+--------------------------------------------------+ | appendfsync | Controls how often fsync() transfers cached data to the disk. Note that some OSs will perform a complete data transfer but some others only make a "best-effort" attempt. | - no | everysec | | | | - always | | @@ -85,8 +87,11 @@ Procedure +-----------------------------------------------+---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+--------------------------------------------------+--------------------------------------------------+ | master-read-only | Sets the instance to be read-only. All write operations will fail. | - yes | no | | | | - no | | + | | Proxy Cluster instances do not have this parameter. | | | +-----------------------------------------------+---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+--------------------------------------------------+--------------------------------------------------+ | maxclients | The maximum number of clients allowed to be concurrently connected to a DCS instance. | Depends on the instance type and specifications. | Depends on the instance type and specifications. | + | | | | | + | | Proxy Cluster instances do not have this parameter. | | | +-----------------------------------------------+---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+--------------------------------------------------+--------------------------------------------------+ | proto-max-bulk-len | Maximum size of a single element request (in bytes). | 1,048,576-536,870,912 | 536,870,912 | +-----------------------------------------------+---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+--------------------------------------------------+--------------------------------------------------+ @@ -139,6 +144,8 @@ Procedure | | **A**: an alias for "g$lshzxe" | | | | | | | | | | The parameter value must contain either **K** or **E**. **A** cannot be used together with any of the characters in "g$lshzxe". For example, the value **Kl** means that Redis will notify Pub/Sub clients about keyspace events and list commands. The value **AKE** means Redis will notify Pub/Sub clients about all events. | | | + | | | | | + | | Proxy Cluster instances do not have this parameter. | | | +-----------------------------------------------+---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+--------------------------------------------------+--------------------------------------------------+ | slowlog-log-slower-than | Redis records queries that exceed a specified execution time. | 0-1,000,000 | 10,000 | | | | | | @@ -157,6 +164,8 @@ Procedure - **A** is an alias for "g$lshzxe" and cannot be used together with any of the characters in "g$lshzxe". - For example, the value **Kl** means that Redis will notify Pub/Sub clients about keyspace events and list commands. The value **AKE** means Redis will notify Pub/Sub clients about all events. + d. Configurable parameters and their values vary depending on the instance type. + #. After you have finished setting the parameters, click **Save**. #. Click **Yes** to confirm the modification. diff --git a/umn/source/operation_guide/managing_dcs_instances/modifying_maintenance_time_window.rst b/umn/source/operation_guide/managing_dcs_instances/modifying_maintenance_time_window.rst index 94b209b..8b321fa 100644 --- a/umn/source/operation_guide/managing_dcs_instances/modifying_maintenance_time_window.rst +++ b/umn/source/operation_guide/managing_dcs_instances/modifying_maintenance_time_window.rst @@ -31,5 +31,5 @@ Procedure .. |image1| image:: /_static/images/en-us_image_0000001148443456.png .. |image2| image:: /_static/images/en-us_image_0266235581.jpg -.. |image3| image:: /_static/images/en-us_image_0266235565.jpg -.. |image4| image:: /_static/images/en-us_image_0266235461.jpg +.. |image3| image:: /_static/images/en-us_image_0266235415.png +.. |image4| image:: /_static/images/en-us_image_0266235408.png diff --git a/umn/source/operation_guide/managing_dcs_instances/modifying_the_security_group.rst b/umn/source/operation_guide/managing_dcs_instances/modifying_the_security_group.rst index 78af676..4c7b321 100644 --- a/umn/source/operation_guide/managing_dcs_instances/modifying_the_security_group.rst +++ b/umn/source/operation_guide/managing_dcs_instances/modifying_the_security_group.rst @@ -7,7 +7,7 @@ Modifying the Security Group On the DCS console, after creating a DCS instance, you can modify the security group of the DCS instance on the instance's **Basic Information** page. -You can modify the security groups of DCS Redis 3.0 instances but cannot modify those of DCS Redis 4.0 or 5.0 instances. +You can modify the security groups of DCS Redis 3.0 instances but cannot modify those of DCS Redis 4.0/5.0/6.0 instances. Prerequisites ------------- @@ -37,5 +37,5 @@ Procedure .. |image1| image:: /_static/images/en-us_image_0000001194403153.png .. |image2| image:: /_static/images/en-us_image_0266235582.png -.. |image3| image:: /_static/images/en-us_image_0266235565.jpg -.. |image4| image:: /_static/images/en-us_image_0266235461.jpg +.. |image3| image:: /_static/images/en-us_image_0266235377.png +.. |image4| image:: /_static/images/en-us_image_0266235369.png diff --git a/umn/source/operation_guide/migrating_data_with_dcs/importing_backup_files/importing_backup_files_from_an_obs_bucket.rst b/umn/source/operation_guide/migrating_data_with_dcs/importing_backup_files/importing_backup_files_from_an_obs_bucket.rst index a560ad8..c77640b 100644 --- a/umn/source/operation_guide/migrating_data_with_dcs/importing_backup_files/importing_backup_files_from_an_obs_bucket.rst +++ b/umn/source/operation_guide/migrating_data_with_dcs/importing_backup_files/importing_backup_files_from_an_obs_bucket.rst @@ -35,7 +35,7 @@ Step 1: Prepare the Target DCS Redis Instance - If the target instance is Redis 4.0 or 5.0, clear the data by referring to :ref:`Clearing DCS Instance Data `. - If the target instance is a DCS Redis 3.0 instance, run the **FLUSHALL** command to clear data. -You can use a DCS Redis 3.0, 4.0, or 5.0 instance as the target instance. +You can use a DCS Redis 3.0/4.0/5.0 instance as the target instance. Step 2: Create an OBS Bucket and Upload Backup Files ---------------------------------------------------- diff --git a/umn/source/operation_guide/migrating_data_with_dcs/importing_backup_files/importing_backup_files_from_redis.rst b/umn/source/operation_guide/migrating_data_with_dcs/importing_backup_files/importing_backup_files_from_redis.rst index bcd2163..72d46a9 100644 --- a/umn/source/operation_guide/migrating_data_with_dcs/importing_backup_files/importing_backup_files_from_redis.rst +++ b/umn/source/operation_guide/migrating_data_with_dcs/importing_backup_files/importing_backup_files_from_redis.rst @@ -35,7 +35,7 @@ Step 2: Prepare the Target DCS Redis Instance - If the target instance is Redis 4.0 or 5.0, clear the data by referring to :ref:`Clearing DCS Instance Data `. - If the target instance is a DCS Redis 3.0 instance, run the **FLUSHALL** command to clear data. -You can use a DCS Redis 3.0, 4.0, or 5.0 instance as the target instance. +You can use a DCS Redis 3.0/4.0/5.0 instance as the target instance. Step 3: Create a Migration Task ------------------------------- diff --git a/umn/source/operation_guide/operating_dcs_instances/clearing_dcs_instance_data.rst b/umn/source/operation_guide/operating_dcs_instances/clearing_dcs_instance_data.rst index 3bf686c..d0ed50b 100644 --- a/umn/source/operation_guide/operating_dcs_instances/clearing_dcs_instance_data.rst +++ b/umn/source/operation_guide/operating_dcs_instances/clearing_dcs_instance_data.rst @@ -5,7 +5,7 @@ Clearing DCS Instance Data ========================== -On the DCS console, you can clear data only for DCS Redis 4.0 and 5.0 instances. +You can clear data of DCS Redis 4.0 and later instances on the console. **Clearing instance data cannot be undone and cleared data cannot be recovered. Exercise caution when performing this operation.** @@ -15,7 +15,7 @@ Procedure #. Log in to the DCS console. #. Click |image1| in the upper left corner and select a region and a project. #. In the navigation pane, choose **Cache Manager**. -#. Select one or more DCS2.0 instances to clear. +#. Select one or more DCS instances. #. Click **Clear data** above the instance list. #. In the displayed dialog box, click **Yes**. diff --git a/umn/source/operation_guide/operating_dcs_instances/command_renaming.rst b/umn/source/operation_guide/operating_dcs_instances/command_renaming.rst index 8600c81..d637cd1 100644 --- a/umn/source/operation_guide/operating_dcs_instances/command_renaming.rst +++ b/umn/source/operation_guide/operating_dcs_instances/command_renaming.rst @@ -5,7 +5,7 @@ Command Renaming ================ -After creating a DCS Redis 4.0 or 5.0 instance, you can rename the following critical commands: **COMMAND**, **KEYS**, **FLUSHDB**, **FLUSHALL**, and **HGETALL**. +After creating a DCS Redis 4.0 or later instance, you can rename the following critical commands: Currently, you can only rename the **COMMAND**, **KEYS**, **FLUSHDB**, and **FLUSHALL** commands. Procedure --------- diff --git a/umn/source/operation_guide/operating_dcs_instances/exporting_dcs_instance_list.rst b/umn/source/operation_guide/operating_dcs_instances/exporting_dcs_instance_list.rst index abb8063..7f3328b 100644 --- a/umn/source/operation_guide/operating_dcs_instances/exporting_dcs_instance_list.rst +++ b/umn/source/operation_guide/operating_dcs_instances/exporting_dcs_instance_list.rst @@ -16,8 +16,6 @@ Procedure #. In the navigation pane, choose **Cache Manager**. -#. Click the search bar. In the displayed drop-down list, select the filter criteria to query the desired DCS instances. - #. Click |image2| above the instance list. Click the export result displayed in the lower left corner of the page. diff --git a/umn/source/operation_guide/operating_dcs_instances/modifying_dcs_instance_specifications.rst b/umn/source/operation_guide/operating_dcs_instances/modifying_dcs_instance_specifications.rst index a8cbc94..a373079 100644 --- a/umn/source/operation_guide/operating_dcs_instances/modifying_dcs_instance_specifications.rst +++ b/umn/source/operation_guide/operating_dcs_instances/modifying_dcs_instance_specifications.rst @@ -26,6 +26,7 @@ Scaling Redis 3.0 Scaling up/down Scaling up/down N/A Scaling up Redis 4.0 Scaling up/down Scaling up/down Scaling up N/A Redis 5.0 Scaling up/down Scaling up/down Scaling up N/A + Redis 6.0 Scaling up/down Scaling up/down N/A N/A ============ =============== =============== ============= ============= .. note:: @@ -36,11 +37,11 @@ Scaling - Single-node and master/standby - - A DCS Redis 4.0 or 5.0 instance will be disconnected for several seconds and remain read-only for about 1 minute. + - A DCS Redis 4.0/5.0/6.0 instance will be disconnected for several seconds and remain read-only for about 1 minute. - A DCS Redis 3.0 instance will be disconnected and remain read-only for 5 to 30 minutes. - For scaling up, only the memory of the instance is expanded. The CPU processing capability is not improved. - Data of single-node instances may be lost because they do not support data persistence. After scaling, check whether the data is complete and import data if required. - - Backup records of master/standby instances cannot be restored after scaling down. + - Backup records of master/standby instances cannot be used after scaling down. - Cluster diff --git a/umn/source/operation_guide/operating_dcs_instances/restarting_dcs_instances.rst b/umn/source/operation_guide/operating_dcs_instances/restarting_dcs_instances.rst index ea0167f..6536120 100644 --- a/umn/source/operation_guide/operating_dcs_instances/restarting_dcs_instances.rst +++ b/umn/source/operation_guide/operating_dcs_instances/restarting_dcs_instances.rst @@ -33,7 +33,7 @@ Procedure #. In the displayed dialog box, click **Yes**. - It takes 1 to 30 minutes to restart DCS instances. After DCS instances are restarted, their status changes to **Running**. + It takes 10 seconds to 30 minutes to restart DCS instances. After DCS instances are restarted, their status changes to **Running**. .. note:: diff --git a/umn/source/service_overview/command_compatibility/index.rst b/umn/source/service_overview/command_compatibility/index.rst index 06191b1..060d497 100644 --- a/umn/source/service_overview/command_compatibility/index.rst +++ b/umn/source/service_overview/command_compatibility/index.rst @@ -8,6 +8,7 @@ Command Compatibility - :ref:`Redis 3.0 Commands ` - :ref:`Redis 4.0 Commands ` - :ref:`Redis 5.0 Commands ` +- :ref:`Redis 6.0 Commands ` - :ref:`Web CLI Commands ` - :ref:`Command Restrictions for Cluster Instances ` - :ref:`Other Command Usage Restrictions ` @@ -19,6 +20,7 @@ Command Compatibility redis_3.0_commands redis_4.0_commands redis_5.0_commands + redis_6.0_commands web_cli_commands command_restrictions_for_cluster_instances other_command_usage_restrictions diff --git a/umn/source/service_overview/command_compatibility/redis_4.0_commands.rst b/umn/source/service_overview/command_compatibility/redis_4.0_commands.rst index edbae5e..654fa62 100644 --- a/umn/source/service_overview/command_compatibility/redis_4.0_commands.rst +++ b/umn/source/service_overview/command_compatibility/redis_4.0_commands.rst @@ -96,7 +96,7 @@ Commands Supported by DCS for Redis 4.0 +---------------------------------------------------------+------------------------------------------------+-----------------------------------------------------------+-------------------------------------------------------+-----------------------------------------------------+-----------------------------------------+ | ``-`` | PUNSUBSCRIBE | UNWATCH | QUIT | SCRIPT FLUSH | GEODIST | +---------------------------------------------------------+------------------------------------------------+-----------------------------------------------------------+-------------------------------------------------------+-----------------------------------------------------+-----------------------------------------+ - | ``-`` | SUBSCRIBE | WATCH | SELECT | SCRIPT KILL | GEORADIUS | + | ``-`` | SUBSCRIBE | WATCH | SELECT (not supported by Redis Cluster instances) | SCRIPT KILL | GEORADIUS | +---------------------------------------------------------+------------------------------------------------+-----------------------------------------------------------+-------------------------------------------------------+-----------------------------------------------------+-----------------------------------------+ | ``-`` | UNSUBSCRIBE | ``-`` | ``-`` | SCRIPT LOAD | GEORADIUSBYMEMBER | +---------------------------------------------------------+------------------------------------------------+-----------------------------------------------------------+-------------------------------------------------------+-----------------------------------------------------+-----------------------------------------+ diff --git a/umn/source/service_overview/command_compatibility/redis_5.0_commands.rst b/umn/source/service_overview/command_compatibility/redis_5.0_commands.rst index 321bde2..80506bb 100644 --- a/umn/source/service_overview/command_compatibility/redis_5.0_commands.rst +++ b/umn/source/service_overview/command_compatibility/redis_5.0_commands.rst @@ -94,7 +94,7 @@ Commands Supported by DCS for Redis 5.0 +---------------------------------------------------------+------------------------------------------------+-----------------------------------------------------------+-------------------------------------------------------+-----------------------------------------------------+-----------------------------------------+-----------------------------------------------+ | ``-`` | PUNSUBSCRIBE | UNWATCH | QUIT | SCRIPT FLUSH | GEODIST | XDEL | +---------------------------------------------------------+------------------------------------------------+-----------------------------------------------------------+-------------------------------------------------------+-----------------------------------------------------+-----------------------------------------+-----------------------------------------------+ - | ``-`` | SUBSCRIBE | WATCH | SELECT | SCRIPT KILL | GEORADIUS | XGROUP | + | ``-`` | SUBSCRIBE | WATCH | SELECT (not supported by Redis Cluster instances) | SCRIPT KILL | GEORADIUS | XGROUP | +---------------------------------------------------------+------------------------------------------------+-----------------------------------------------------------+-------------------------------------------------------+-----------------------------------------------------+-----------------------------------------+-----------------------------------------------+ | ``-`` | UNSUBSCRIBE | ``-`` | ``-`` | SCRIPT LOAD | GEORADIUSBYMEMBER | XINFO | +---------------------------------------------------------+------------------------------------------------+-----------------------------------------------------------+-------------------------------------------------------+-----------------------------------------------------+-----------------------------------------+-----------------------------------------------+ diff --git a/umn/source/service_overview/command_compatibility/redis_6.0_commands.rst b/umn/source/service_overview/command_compatibility/redis_6.0_commands.rst new file mode 100644 index 0000000..a52bb05 --- /dev/null +++ b/umn/source/service_overview/command_compatibility/redis_6.0_commands.rst @@ -0,0 +1,135 @@ +:original_name: dcs-pd-210209002.html + +.. _dcs-pd-210209002: + +Redis 6.0 Commands +================== + +DCS for Redis 6.0 is compatible with Redis 6.2.7 and with open-source protocols and commands. + +This section describes DCS for Redis 6.0's command compatibility, including supported and disabled commands. + +For more information about the command syntax, visit the `Redis official website `__. + +DCS Redis instances support most Redis commands. Any client compatible with the Redis protocol can access DCS. + +- For security purposes, some Redis commands are disabled in DCS, as listed in :ref:`Commands Disabled by DCS for Redis 6.0 `. +- Some Redis commands (such as **KEYS**, **FLUSHDB**, and **FLUSHALL**) have usage restrictions, which are described in :ref:`Other Command Usage Restrictions `. + +Commands Supported by DCS for Redis 6.0 +--------------------------------------- + +.. table:: **Table 1** Commands supported by DCS for Redis 6.0 (1) + + +-------------------------------------------------------+-----------------------------------------------+-------------------------------------------+-------------------------------------------+-----------------------------------------+-------------------------------------------------------+-----------------------------------------------+ + | `Generic (Key) `__ | `String `__ | `Hash `__ | `List `__ | `Set `__ | `Sorted Set `__ | `Server `__ | + +=======================================================+===============================================+===========================================+===========================================+=========================================+=======================================================+===============================================+ + | DEL | APPEND | HDEL | BLPOP | SADD | ZADD | FLUSHALL | + +-------------------------------------------------------+-----------------------------------------------+-------------------------------------------+-------------------------------------------+-----------------------------------------+-------------------------------------------------------+-----------------------------------------------+ + | DUMP | BITCOUNT | HEXISTS | BRPOP | SCARD | ZCARD | FLUSHDB | + +-------------------------------------------------------+-----------------------------------------------+-------------------------------------------+-------------------------------------------+-----------------------------------------+-------------------------------------------------------+-----------------------------------------------+ + | EXISTS | BITOP | HGET | BRPOPLRUSH | SDIFF | ZCOUNT | DBSIZE | + +-------------------------------------------------------+-----------------------------------------------+-------------------------------------------+-------------------------------------------+-----------------------------------------+-------------------------------------------------------+-----------------------------------------------+ + | EXPIRE | BITPOS | HGETALL | LINDEX | SDIFFSTORE | ZINCRBY | TIME | + +-------------------------------------------------------+-----------------------------------------------+-------------------------------------------+-------------------------------------------+-----------------------------------------+-------------------------------------------------------+-----------------------------------------------+ + | MOVE | DECR | HINCRBY | LINSERT | SINTER | ZRANGE | INFO | + +-------------------------------------------------------+-----------------------------------------------+-------------------------------------------+-------------------------------------------+-----------------------------------------+-------------------------------------------------------+-----------------------------------------------+ + | PERSIST | DECRBY | HINCRBYFLOAT | LLEN | SINTERSTORE | ZRANGEBYSCORE | CLIENT KILL | + +-------------------------------------------------------+-----------------------------------------------+-------------------------------------------+-------------------------------------------+-----------------------------------------+-------------------------------------------------------+-----------------------------------------------+ + | PTTL | GET | HKEYS | LPOP | SISMEMBER | ZRANK | CLIENT LIST | + +-------------------------------------------------------+-----------------------------------------------+-------------------------------------------+-------------------------------------------+-----------------------------------------+-------------------------------------------------------+-----------------------------------------------+ + | RANDOMKEY | GETRANGE | HMGET | LPUSHX | SMEMBERS | ZREMRANGEBYRANK | CLIENT GETNAME | + +-------------------------------------------------------+-----------------------------------------------+-------------------------------------------+-------------------------------------------+-----------------------------------------+-------------------------------------------------------+-----------------------------------------------+ + | RENAME | GETSET | HMSET | LRANGE | SMOVE | ZREMRANGEBYCORE | CLIENT SETNAME | + +-------------------------------------------------------+-----------------------------------------------+-------------------------------------------+-------------------------------------------+-----------------------------------------+-------------------------------------------------------+-----------------------------------------------+ + | RENAMENX | INCR | HSET | LREM | SPOP | ZREVRANGE | CONFIG GET | + +-------------------------------------------------------+-----------------------------------------------+-------------------------------------------+-------------------------------------------+-----------------------------------------+-------------------------------------------------------+-----------------------------------------------+ + | RESTORE | INCRBY | HSETNX | LSET | SRANDMEMBER | ZREVRANGEBYSCORE | MONITOR | + +-------------------------------------------------------+-----------------------------------------------+-------------------------------------------+-------------------------------------------+-----------------------------------------+-------------------------------------------------------+-----------------------------------------------+ + | SORT | INCRBYFLOAT | HVALS | LTRIM | SREM | ZREVRANK | SLOWLOG | + +-------------------------------------------------------+-----------------------------------------------+-------------------------------------------+-------------------------------------------+-----------------------------------------+-------------------------------------------------------+-----------------------------------------------+ + | TTL | MGET | HSCAN | RPOP | SUNION | ZSCORE | ROLE | + +-------------------------------------------------------+-----------------------------------------------+-------------------------------------------+-------------------------------------------+-----------------------------------------+-------------------------------------------------------+-----------------------------------------------+ + | TYPE | MSET | HSTRLEN | RPOPLPU | SUNIONSTORE | ZUNIONSTORE | SWAPDB | + +-------------------------------------------------------+-----------------------------------------------+-------------------------------------------+-------------------------------------------+-----------------------------------------+-------------------------------------------------------+-----------------------------------------------+ + | SCAN | MSETNX | HLEN | RPOPLPUSH | SSCAN | ZINTERSTORE | MEMORY | + +-------------------------------------------------------+-----------------------------------------------+-------------------------------------------+-------------------------------------------+-----------------------------------------+-------------------------------------------------------+-----------------------------------------------+ + | OBJECT | PSETEX | ``-`` | RPUSH | ``-`` | ZSCAN | CONFIG | + +-------------------------------------------------------+-----------------------------------------------+-------------------------------------------+-------------------------------------------+-----------------------------------------+-------------------------------------------------------+-----------------------------------------------+ + | PEXPIREAT | SET | ``-`` | RPUSHX | ``-`` | ZRANGEBYLEX | ``-`` | + +-------------------------------------------------------+-----------------------------------------------+-------------------------------------------+-------------------------------------------+-----------------------------------------+-------------------------------------------------------+-----------------------------------------------+ + | PEXPIRE | SETBIT | ``-`` | LPUSH | ``-`` | ZLEXCOUNT | ``-`` | + +-------------------------------------------------------+-----------------------------------------------+-------------------------------------------+-------------------------------------------+-----------------------------------------+-------------------------------------------------------+-----------------------------------------------+ + | KEYS | SETEX | ``-`` | ``-`` | ``-`` | ZPOPMIN | ``-`` | + +-------------------------------------------------------+-----------------------------------------------+-------------------------------------------+-------------------------------------------+-----------------------------------------+-------------------------------------------------------+-----------------------------------------------+ + | ``-`` | SETNX | ``-`` | ``-`` | ``-`` | ZPOPMAX | ``-`` | + +-------------------------------------------------------+-----------------------------------------------+-------------------------------------------+-------------------------------------------+-----------------------------------------+-------------------------------------------------------+-----------------------------------------------+ + | ``-`` | SETRANGE | ``-`` | ``-`` | ``-`` | ZREMRANGEBYSCORE | ``-`` | + +-------------------------------------------------------+-----------------------------------------------+-------------------------------------------+-------------------------------------------+-----------------------------------------+-------------------------------------------------------+-----------------------------------------------+ + | ``-`` | STRLEN | ``-`` | ``-`` | ``-`` | ZREM | ``-`` | + +-------------------------------------------------------+-----------------------------------------------+-------------------------------------------+-------------------------------------------+-----------------------------------------+-------------------------------------------------------+-----------------------------------------------+ + | ``-`` | BITFIELD | ``-`` | ``-`` | ``-`` | ``-`` | ``-`` | + +-------------------------------------------------------+-----------------------------------------------+-------------------------------------------+-------------------------------------------+-----------------------------------------+-------------------------------------------------------+-----------------------------------------------+ + +.. table:: **Table 2** Commands supported by DCS for Redis 6.0 (2) + + +---------------------------------------------------------+------------------------------------------------+-----------------------------------------------------------+-------------------------------------------------------+-----------------------------------------------------+-----------------------------------------+-----------------------------------------------+ + | `HyperLoglog `__ | `Pub/Sub `__ | `Transactions `__ | `Connection `__ | `Scripting `__ | `Geo `__ | `Stream `__ | + +=========================================================+================================================+===========================================================+=======================================================+=====================================================+=========================================+===============================================+ + | PFADD | PSUBSCRIBE | DISCARD | AUTH | EVAL | GEOADD | XACK | + +---------------------------------------------------------+------------------------------------------------+-----------------------------------------------------------+-------------------------------------------------------+-----------------------------------------------------+-----------------------------------------+-----------------------------------------------+ + | PFCOUNT | PUBLISH | EXEC | ECHO | EVALSHA | GEOHASH | XADD | + +---------------------------------------------------------+------------------------------------------------+-----------------------------------------------------------+-------------------------------------------------------+-----------------------------------------------------+-----------------------------------------+-----------------------------------------------+ + | PFMERGE | PUBSUB | MULTI | PING | SCRIPT EXISTS | GEOPOS | XCLAIM | + +---------------------------------------------------------+------------------------------------------------+-----------------------------------------------------------+-------------------------------------------------------+-----------------------------------------------------+-----------------------------------------+-----------------------------------------------+ + | ``-`` | PUNSUBSCRIBE | UNWATCH | QUIT | SCRIPT FLUSH | GEODIST | XDEL | + +---------------------------------------------------------+------------------------------------------------+-----------------------------------------------------------+-------------------------------------------------------+-----------------------------------------------------+-----------------------------------------+-----------------------------------------------+ + | ``-`` | SUBSCRIBE | WATCH | SELECT | SCRIPT KILL | GEORADIUS | XGROUP | + +---------------------------------------------------------+------------------------------------------------+-----------------------------------------------------------+-------------------------------------------------------+-----------------------------------------------------+-----------------------------------------+-----------------------------------------------+ + | ``-`` | UNSUBSCRIBE | ``-`` | ``-`` | SCRIPT LOAD | GEORADIUSBYMEMBER | XINFO | + +---------------------------------------------------------+------------------------------------------------+-----------------------------------------------------------+-------------------------------------------------------+-----------------------------------------------------+-----------------------------------------+-----------------------------------------------+ + | ``-`` | ``-`` | ``-`` | ``-`` | ``-`` | ``-`` | XLEN | + +---------------------------------------------------------+------------------------------------------------+-----------------------------------------------------------+-------------------------------------------------------+-----------------------------------------------------+-----------------------------------------+-----------------------------------------------+ + | ``-`` | ``-`` | ``-`` | ``-`` | ``-`` | ``-`` | XPENDING | + +---------------------------------------------------------+------------------------------------------------+-----------------------------------------------------------+-------------------------------------------------------+-----------------------------------------------------+-----------------------------------------+-----------------------------------------------+ + | ``-`` | ``-`` | ``-`` | ``-`` | ``-`` | ``-`` | XRANGE | + +---------------------------------------------------------+------------------------------------------------+-----------------------------------------------------------+-------------------------------------------------------+-----------------------------------------------------+-----------------------------------------+-----------------------------------------------+ + | ``-`` | ``-`` | ``-`` | ``-`` | ``-`` | ``-`` | XREAD | + +---------------------------------------------------------+------------------------------------------------+-----------------------------------------------------------+-------------------------------------------------------+-----------------------------------------------------+-----------------------------------------+-----------------------------------------------+ + | ``-`` | ``-`` | ``-`` | ``-`` | ``-`` | ``-`` | XREADGROUP | + +---------------------------------------------------------+------------------------------------------------+-----------------------------------------------------------+-------------------------------------------------------+-----------------------------------------------------+-----------------------------------------+-----------------------------------------------+ + | ``-`` | ``-`` | ``-`` | ``-`` | ``-`` | ``-`` | XREVRANGE | + +---------------------------------------------------------+------------------------------------------------+-----------------------------------------------------------+-------------------------------------------------------+-----------------------------------------------------+-----------------------------------------+-----------------------------------------------+ + | ``-`` | ``-`` | ``-`` | ``-`` | ``-`` | ``-`` | XTRIM | + +---------------------------------------------------------+------------------------------------------------+-----------------------------------------------------------+-------------------------------------------------------+-----------------------------------------------------+-----------------------------------------+-----------------------------------------------+ + +.. _dcs-pd-210209002__section1153718441417: + +Commands Disabled by DCS for Redis 6.0 +-------------------------------------- + +.. table:: **Table 3** Redis commands disabled in DCS Redis 6.0 instances + + +-------------------------------------------------------+-----------------------------------------------+ + | `Generic (Key) `__ | `Server `__ | + +=======================================================+===============================================+ + | MIGRATE | SLAVEOF | + +-------------------------------------------------------+-----------------------------------------------+ + | ``-`` | SHUTDOWN | + +-------------------------------------------------------+-----------------------------------------------+ + | ``-`` | LASTSAVE | + +-------------------------------------------------------+-----------------------------------------------+ + | ``-`` | DEBUG commands | + +-------------------------------------------------------+-----------------------------------------------+ + | ``-`` | COMMAND | + +-------------------------------------------------------+-----------------------------------------------+ + | ``-`` | SAVE | + +-------------------------------------------------------+-----------------------------------------------+ + | ``-`` | BGSAVE | + +-------------------------------------------------------+-----------------------------------------------+ + | ``-`` | BGREWRITEAOF | + +-------------------------------------------------------+-----------------------------------------------+ + | ``-`` | SYNC | + +-------------------------------------------------------+-----------------------------------------------+ + | ``-`` | PSYNC | + +-------------------------------------------------------+-----------------------------------------------+ diff --git a/umn/source/service_overview/command_compatibility/web_cli_commands.rst b/umn/source/service_overview/command_compatibility/web_cli_commands.rst index cf465bb..b822417 100644 --- a/umn/source/service_overview/command_compatibility/web_cli_commands.rst +++ b/umn/source/service_overview/command_compatibility/web_cli_commands.rst @@ -7,7 +7,7 @@ Web CLI Commands Web CLI is a command line tool provided on the DCS console. This section describes Web CLI's compatibility with Redis commands, including supported and disabled commands. For details about the command syntax, visit the `Redis official website `__. -**Currently, only DCS for Redis 4.0 and 5.0 support Web CLI.** +**Currently, only DCS for Redis 4.0/5.0 support Web CLI.** .. note:: diff --git a/umn/source/service_overview/comparing_dcs_and_open-source_cache_services.rst b/umn/source/service_overview/comparing_dcs_and_open-source_cache_services.rst index 08b1ece..a1af522 100644 --- a/umn/source/service_overview/comparing_dcs_and_open-source_cache_services.rst +++ b/umn/source/service_overview/comparing_dcs_and_open-source_cache_services.rst @@ -18,9 +18,9 @@ DCS for Redis vs. Open-Source Redis | Feature | Open-Source Redis | DCS for Redis | +========================+==================================================================================================================================================+============================================================================================================================================================================+ | Service deployment | Requires 0.5 to 2 days to prepare servers. | - Creates a Redis 3.0 instance in 5 to 15 minutes. | - | | | - Creates a containerized Redis 4.0 or 5.0 instance within 8 seconds. | + | | | - Creates a containerized Redis 4.0 or later instance within 8 seconds. | +------------------------+--------------------------------------------------------------------------------------------------------------------------------------------------+----------------------------------------------------------------------------------------------------------------------------------------------------------------------------+ - | Version | ``-`` | Deeply engaged in the open-source community and supports the latest Redis version. Currently, Redis 3.0, 4.0, and 5.0 are supported. | + | Version | ``-`` | Deeply engaged in the open-source community and supports the latest Redis version. Redis 3.0/4.0/5.0/6.0 are supported. | +------------------------+--------------------------------------------------------------------------------------------------------------------------------------------------+----------------------------------------------------------------------------------------------------------------------------------------------------------------------------+ | Security | Network and server safety is the user's responsibility. | - Network security is ensured using VPCs and security groups. | | | | - Data reliability is ensured by data replication and scheduled backup. | diff --git a/umn/source/service_overview/comparing_redis_versions.rst b/umn/source/service_overview/comparing_redis_versions.rst index 59ef6d3..b2b4e09 100644 --- a/umn/source/service_overview/comparing_redis_versions.rst +++ b/umn/source/service_overview/comparing_redis_versions.rst @@ -9,27 +9,27 @@ When creating a DCS Redis instance, you can select the cache engine version and - **Version** - DCS supports Redis 3.0, 4.0, and 5.0. The following table describes the differences between these versions. + DCS supports Redis 3.0/4.0/5.0/6.0. The following table describes the differences between these versions. .. table:: **Table 1** Differences between Redis versions - +----------------------------------------+-------------------------------------------------------+--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+ - | Feature | Redis 3.0 | Redis 4.0 and Redis 5.0 | - +========================================+=======================================================+==================================================================================================================================================================================================+ - | Instance deployment mode | Based on VMs | Containerized based on physical servers | - +----------------------------------------+-------------------------------------------------------+--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+ - | Time required for creating an instance | 3-15 minutes, or 10-30 minutes for cluster instances. | 8 seconds | - +----------------------------------------+-------------------------------------------------------+--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+ - | QPS | 100,000 QPS per node | 100,000 QPS per node | - +----------------------------------------+-------------------------------------------------------+--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+ - | Instance type | Single-node, master/standby, and Proxy Cluster | Single-node, master/standby and Redis Cluster | - +----------------------------------------+-------------------------------------------------------+--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+ - | Instance total memory | Ranges from 2 GB, 4 GB, 8 GB, to 1024 GB. | Regular specifications range from 2 GB, 4 GB, 8 GB, to 1024 GB. Small specifications, such as 128 MB, 256 MB, 512 MB, and 1 GB, are also available for single-node and master/standby instances. | - +----------------------------------------+-------------------------------------------------------+--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+ - | Scale-up or scale-down | Online scale-up and scale-down | Online scale-up and scale-down | - +----------------------------------------+-------------------------------------------------------+--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+ - | Backup and restoration | Supported for master/standby and cluster instances | Supported for master/standby and cluster instances | - +----------------------------------------+-------------------------------------------------------+--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+ + +----------------------------------------+-------------------------------------------------------+--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+------------------------------------------------------------------------------------------------------------------------+ + | Feature | Redis 3.0 | Redis 4.0 & Redis 5.0 | Redis 6.0 | + +========================================+=======================================================+==================================================================================================================================================================================================+========================================================================================================================+ + | Instance deployment mode | Based on VMs | Containerized based on physical servers | Containerized based on physical servers | + +----------------------------------------+-------------------------------------------------------+--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+------------------------------------------------------------------------------------------------------------------------+ + | Time required for creating an instance | 3-15 minutes, or 10-30 minutes for cluster instances. | 8 seconds | 8 seconds | + +----------------------------------------+-------------------------------------------------------+--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+------------------------------------------------------------------------------------------------------------------------+ + | QPS | 100,000 QPS per node | 100,000 QPS per node | 150,000 QPS per node | + +----------------------------------------+-------------------------------------------------------+--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+------------------------------------------------------------------------------------------------------------------------+ + | Instance type | Single-node, master/standby, and Proxy Cluster | Single-node, master/standby and Redis Cluster | Single-node and master/standby | + +----------------------------------------+-------------------------------------------------------+--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+------------------------------------------------------------------------------------------------------------------------+ + | Instance total memory | Ranges from 2 GB, 4 GB, 8 GB, to 1024 GB. | Regular specifications range from 2 GB, 4 GB, 8 GB, to 1024 GB. Small specifications, such as 128 MB, 256 MB, 512 MB, and 1 GB, are also available for single-node and master/standby instances. | 2 GB, 4 GB, 8 GB, 16 GB, 32 GB, and 64 GB. Small specifications (128 MB, 256 MB, 512 MB, and 1 GB) are also supported. | + +----------------------------------------+-------------------------------------------------------+--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+------------------------------------------------------------------------------------------------------------------------+ + | Scale-up or scale-down | Online scale-up and scale-down | Online scale-up and scale-down | Online scale-up and scale-down | + +----------------------------------------+-------------------------------------------------------+--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+------------------------------------------------------------------------------------------------------------------------+ + | Backup and restoration | Supported for master/standby and cluster instances | Supported for master/standby and cluster instances | Supported for master/standby instances | + +----------------------------------------+-------------------------------------------------------+--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+------------------------------------------------------------------------------------------------------------------------+ .. note:: diff --git a/umn/source/service_overview/dcs_instance_specifications/index.rst b/umn/source/service_overview/dcs_instance_specifications/index.rst index 1b999f3..a020c9c 100644 --- a/umn/source/service_overview/dcs_instance_specifications/index.rst +++ b/umn/source/service_overview/dcs_instance_specifications/index.rst @@ -7,6 +7,7 @@ DCS Instance Specifications - :ref:`Redis 3.0 Instance Specifications ` - :ref:`Redis 4.0 and 5.0 Instance Specifications ` +- :ref:`Redis 6.0 Instance Specifications ` .. toctree:: :maxdepth: 1 @@ -14,3 +15,4 @@ DCS Instance Specifications redis_3.0_instance_specifications redis_4.0_and_5.0_instance_specifications + redis_6.0_instance_specifications diff --git a/umn/source/service_overview/dcs_instance_specifications/redis_6.0_instance_specifications.rst b/umn/source/service_overview/dcs_instance_specifications/redis_6.0_instance_specifications.rst new file mode 100644 index 0000000..b17e272 --- /dev/null +++ b/umn/source/service_overview/dcs_instance_specifications/redis_6.0_instance_specifications.rst @@ -0,0 +1,87 @@ +:original_name: dcs-pd-0916004.html + +.. _dcs-pd-0916004: + +Redis 6.0 Instance Specifications +================================= + +This section describes DCS Redis 6.0 instance specifications, including the total memory, available memory, maximum number of connections allowed, maximum/assured bandwidth, and reference performance. + +The following metrics are related to the instance specifications: + +- Used memory: You can check the memory usage of an instance by viewing the **Memory Usage** and **Used Memory** metrics. +- Maximum connections: The maximum number of connections allowed is the maximum number of clients that can be connected to an instance. To check the number of connections to an instance, view the **Connected Clients** metric. +- QPS represents queries per second, which is the number of commands processed per second. +- Bandwidth: You can view the **Flow Control Times** metric to check whether the bandwidth has exceeded the limit. + +Currently, DCS for Redis 6.0 supports single-node and master/standby instances based on x86 CPUs. + +Single-Node +----------- + +.. table:: **Table 1** Specifications of single-node DCS Redis 6.0 instances + + +--------------+------------------+----------------------------------+---------------------------+-----------------------+ + | Total Memory | Available Memory | Max. Connections (Default/Limit) | Assured/Maximum Bandwidth | Reference Performance | + | | | | | | + | (GB) | (GB) | (Count) | (Mbit/s) | (QPS) | + +==============+==================+==================================+===========================+=======================+ + | 0.125 | 0.125 | 10,000/10,000 | 40/40 | 140,000 | + +--------------+------------------+----------------------------------+---------------------------+-----------------------+ + | 0.25 | 0.25 | 10,000/10,000 | 80/80 | 140,000 | + +--------------+------------------+----------------------------------+---------------------------+-----------------------+ + | 0.5 | 0.5 | 10,000/10,000 | 80/80 | 140,000 | + +--------------+------------------+----------------------------------+---------------------------+-----------------------+ + | 1 | 1 | 10,000/50,000 | 80/80 | 140,000 | + +--------------+------------------+----------------------------------+---------------------------+-----------------------+ + | 2 | 2 | 10,000/50,000 | 128/128 | 140,000 | + +--------------+------------------+----------------------------------+---------------------------+-----------------------+ + | 4 | 4 | 10,000/50,000 | 192/192 | 170,000 | + +--------------+------------------+----------------------------------+---------------------------+-----------------------+ + | 8 | 8 | 10,000/50,000 | 192/192 | 170,000 | + +--------------+------------------+----------------------------------+---------------------------+-----------------------+ + | 16 | 16 | 10,000/50,000 | 256/256 | 170,000 | + +--------------+------------------+----------------------------------+---------------------------+-----------------------+ + | 24 | 24 | 10,000/50,000 | 256/256 | 170,000 | + +--------------+------------------+----------------------------------+---------------------------+-----------------------+ + | 32 | 32 | 10,000/50,000 | 256/256 | 170,000 | + +--------------+------------------+----------------------------------+---------------------------+-----------------------+ + | 48 | 48 | 10,000/50,000 | 256/256 | 170,000 | + +--------------+------------------+----------------------------------+---------------------------+-----------------------+ + | 64 | 64 | 10,000/50,000 | 384/384 | 170,000 | + +--------------+------------------+----------------------------------+---------------------------+-----------------------+ + +Master/Standby +-------------- + +.. table:: **Table 2** Specifications of master/standby DCS Redis 6.0 instances + + +--------------+------------------+----------------------------------+---------------------------+-----------------------+ + | Total Memory | Available Memory | Max. Connections (Default/Limit) | Assured/Maximum Bandwidth | Reference Performance | + | | | | | | + | (GB) | (GB) | (Count) | (Mbit/s) | (QPS) | + +==============+==================+==================================+===========================+=======================+ + | 0.125 | 0.125 | 10,000/10,000 | 40/40 | 120,000 | + +--------------+------------------+----------------------------------+---------------------------+-----------------------+ + | 0.25 | 0.25 | 10,000/10,000 | 80/80 | 120,000 | + +--------------+------------------+----------------------------------+---------------------------+-----------------------+ + | 0.5 | 0.5 | 10,000/10,000 | 80/80 | 120,000 | + +--------------+------------------+----------------------------------+---------------------------+-----------------------+ + | 1 | 1 | 10,000/50,000 | 80/80 | 120,000 | + +--------------+------------------+----------------------------------+---------------------------+-----------------------+ + | 2 | 2 | 10,000/50,000 | 128/128 | 120,000 | + +--------------+------------------+----------------------------------+---------------------------+-----------------------+ + | 4 | 4 | 10,000/50,000 | 192/192 | 150,000 | + +--------------+------------------+----------------------------------+---------------------------+-----------------------+ + | 8 | 8 | 10,000/50,000 | 192/192 | 150,000 | + +--------------+------------------+----------------------------------+---------------------------+-----------------------+ + | 16 | 16 | 10,000/50,000 | 256/256 | 150,000 | + +--------------+------------------+----------------------------------+---------------------------+-----------------------+ + | 24 | 24 | 10,000/50,000 | 256/256 | 150,000 | + +--------------+------------------+----------------------------------+---------------------------+-----------------------+ + | 32 | 32 | 10,000/50,000 | 256/256 | 150,000 | + +--------------+------------------+----------------------------------+---------------------------+-----------------------+ + | 48 | 48 | 10,000/50,000 | 256/256 | 150,000 | + +--------------+------------------+----------------------------------+---------------------------+-----------------------+ + | 64 | 64 | 10,000/50,000 | 384/384 | 150,000 | + +--------------+------------------+----------------------------------+---------------------------+-----------------------+ diff --git a/umn/source/service_overview/dcs_instance_types/master_standby_redis.rst b/umn/source/service_overview/dcs_instance_types/master_standby_redis.rst index 70f89b2..2dc0cda 100644 --- a/umn/source/service_overview/dcs_instance_types/master_standby_redis.rst +++ b/umn/source/service_overview/dcs_instance_types/master_standby_redis.rst @@ -5,11 +5,11 @@ Master/Standby Redis ==================== -This section describes master/standby DCS Redis instances. Three Redis versions are available for master/standby DCS Redis instances: Redis 3.0, Redis 4.0, and Redis 5.0. +This section describes master/standby DCS Redis instances. Redis versions available for master/standby DCS Redis instances include Redis 3.0, 4.0, 5.0, and 6.0. .. note:: - You cannot upgrade the Redis version for an instance. For example, a master/standby DCS Redis 3.0 instance cannot be upgraded to a master/standby DCS Redis 4.0 or 5.0 instance. If your service requires the features of higher Redis versions, create a DCS Redis instance of a higher version and then migrate data from the old instance to the new one. + You cannot upgrade the Redis version for an instance. For example, a master/standby DCS Redis 4.0 instance cannot be upgraded to a master/standby DCS Redis 5.0 instance. If your service requires the features of higher Redis versions, create a DCS Redis instance of a higher version and then migrate data from the old instance to the new one. Features -------- @@ -47,7 +47,7 @@ Architecture .. note:: - To access a DCS Redis 3.0 instance, you must use port 6379. To access a DCS Redis 4.0 or 5.0 instance, you can customize the port. If no port is specified, the default port 6379 will be used. In the following architecture, port 6379 is used. If you have customized a port, replace **6379** with the actual port. + Redis 3.0 does not support port customization and allows only port 6379. For Redis 4.0 and later, you can specify a port or use the default port 6379. In the following architecture, port 6379 is used. If you have customized a port, replace **6379** with the actual port. .. _cachemasterslave__fig14477142816340: diff --git a/umn/source/service_overview/dcs_instance_types/single-node_redis.rst b/umn/source/service_overview/dcs_instance_types/single-node_redis.rst index 5acc6b1..212b799 100644 --- a/umn/source/service_overview/dcs_instance_types/single-node_redis.rst +++ b/umn/source/service_overview/dcs_instance_types/single-node_redis.rst @@ -5,7 +5,7 @@ Single-Node Redis ================= -Three Redis versions are available for single-node DCS Redis instances: Redis 3.0, Redis 4.0, and Redis 5.0. +Single-node DCS Redis instances are available in versions 3.0/4.0/5.0/6.0. Features -------- @@ -35,7 +35,7 @@ Architecture .. note:: - To access a DCS Redis 3.0 instance, you must use port 6379. To access a DCS Redis 4.0 or 5.0 instance, you can customize the port. If no port is specified, the default port 6379 will be used. In the following architecture, port 6379 is used. If you have customized a port, replace **6379** with the actual port. + To access a DCS Redis 3.0 instance, you must use port 6379. To access a DCS Redis 4.0/5.0/6.0 instance, you can customize the port. If no port is specified, the default port 6379 will be used. In the following architecture, port 6379 is used. If you have customized a port, replace **6379** with the actual port. .. _cachesinglenode__fig15457185394718: diff --git a/umn/source/service_overview/ha_and_dr_policies.rst b/umn/source/service_overview/ha_and_dr_policies.rst index 96d1aec..a3f57d0 100644 --- a/umn/source/service_overview/ha_and_dr_policies.rst +++ b/umn/source/service_overview/ha_and_dr_policies.rst @@ -18,7 +18,7 @@ To meet the reliability requirements of your data and services, you can choose t Single-AZ HA ------------ -Single-AZ deployment means deploying an instance within a physical equipment room. DCS provides process/service HA, data persistence, and hot standby DR policies for different types of DCS instances. +Single-AZ deployment means to deploy an instance within a physical equipment room. DCS provides process/service HA, data persistence, and hot standby DR policies for different types of DCS instances. **Single-node DCS instance**: When DCS detects a process fault, a new process is started to ensure service HA. diff --git a/umn/source/service_overview/what_is_dcs.rst b/umn/source/service_overview/what_is_dcs.rst index bf3e09b..5c6309c 100644 --- a/umn/source/service_overview/what_is_dcs.rst +++ b/umn/source/service_overview/what_is_dcs.rst @@ -11,7 +11,7 @@ Distributed Cache Service (DCS) is an online, distributed, in-memory cache servi DCS provides single-node, master/standby, and cluster instances with specifications ranging from 128 MB to 1024 GB. DCS instances can be created with just a few clicks on the console, without requiring you to prepare servers. - DCS Redis 3.0 instances are deployed on VMs. DCS Redis 4.0 and 5.0 instances are containerized and can be created within seconds. + DCS Redis 3.0 instances are deployed on VMs. DCS Redis 4.0/5.0/6.0 instances are containerized and can be created within seconds. - Security and reliability @@ -51,7 +51,7 @@ DCS Redis instances can be customized based on your requirements. +-----------------------------------+---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+ | Instance specification | DCS for Redis provides instances of different specifications, ranging from 128 MB to 1024 GB. | +-----------------------------------+---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+ - | Redis version | DCS instances are compatible with open-source Redis 3.0, 4.0, and 5.0. | + | Redis version | DCS instances are compatible with open-source Redis 3.0, 4.0, 5.0, and 6.0. | +-----------------------------------+---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+ | Underlying architecture | **Standard** Redis based on VMs: supports up to 100,000 queries per second (QPS) at a single node. | +-----------------------------------+---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+