From a801aab463a2bc23829ebe4e5b6c5c50b5b71f2f Mon Sep 17 00:00:00 2001 From: OpenTelekomCloud Proposal Bot Date: Mon, 31 Oct 2022 13:09:05 +0000 Subject: [PATCH] Update content --- .../viewing_traces_on_the_cts_console.rst | 2 - ...instance_through_redis_desktop_manager.rst | 1 - .../security_group_configurations.rst | 2 - ...subcommand_is_displayed_in_springcloud.rst | 1 - ...s_for_redis_support_multiple_databases.rst | 2 +- .../access_in_different_languages/c#.rst | 3 +- .../clients_in_python.rst | 5 +- .../go-redis.rst | 2 +- .../access_in_different_languages/node.js.rst | 4 +- .../creating_a_dcs_redis_instance.rst | 2 +- ...uring_alarm_rules_for_critical_metrics.rst | 10 +- umn/source/monitoring/dcs_metrics.rst | 262 +++++++++--------- .../configuring_a_backup_policy.rst | 2 +- .../managing_shards_and_replicas.rst | 1 - .../modifying_configuration_parameters.rst | 30 +- .../viewing_redis_slow_logs.rst | 1 - .../changing_instance_passwords.rst | 2 +- .../dcs_instance_passwords.rst | 2 +- .../introduction_to_migration_with_dcs.rst | 10 +- .../modifying_dcs_instance_specifications.rst | 2 +- ...ng_a_user_and_granting_dcs_permissions.rst | 1 - .../comparing_redis_versions.rst | 2 +- .../master_standby_redis.rst | 1 - .../proxy_cluster_redis.rst | 1 - .../dcs_instance_types/redis_cluster.rst | 2 - .../dcs_instance_types/single-node_redis.rst | 1 - .../service_overview/ha_and_dr_policies.rst | 5 - .../permissions_management.rst | 36 +-- .../service_overview/related_services.rst | 1 - 29 files changed, 185 insertions(+), 211 deletions(-) diff --git a/umn/source/auditing/viewing_traces_on_the_cts_console.rst b/umn/source/auditing/viewing_traces_on_the_cts_console.rst index 3dd8f4b..8f1fc99 100644 --- a/umn/source/auditing/viewing_traces_on_the_cts_console.rst +++ b/umn/source/auditing/viewing_traces_on_the_cts_console.rst @@ -47,7 +47,6 @@ Procedure .. figure:: /_static/images/en-us_image_0266235352.png :alt: **Figure 1** Expanding trace details - **Figure 1** Expanding trace details #. Click **View Trace** in the **Operation** column. In the dialog box shown in :ref:`Figure 2 `, the trace structure details are displayed. @@ -57,7 +56,6 @@ Procedure .. figure:: /_static/images/en-us_image_0266235315.png :alt: **Figure 2** Viewing traces - **Figure 2** Viewing traces .. |image1| image:: /_static/images/en-us_image_0266235405.png diff --git a/umn/source/faqs/client_and_network_connection/how_do_i_access_a_dcs_redis_instance_through_redis_desktop_manager.rst b/umn/source/faqs/client_and_network_connection/how_do_i_access_a_dcs_redis_instance_through_redis_desktop_manager.rst index 06f4212..e07fc0b 100644 --- a/umn/source/faqs/client_and_network_connection/how_do_i_access_a_dcs_redis_instance_through_redis_desktop_manager.rst +++ b/umn/source/faqs/client_and_network_connection/how_do_i_access_a_dcs_redis_instance_through_redis_desktop_manager.rst @@ -17,7 +17,6 @@ You can access a DCS Redis instance through the Redis Desktop Manager within a V .. figure:: /_static/images/en-us_image_0266315618.png :alt: **Figure 1** Accessing a DCS Redis instance through Redis Desktop Manager over the intranet - **Figure 1** Accessing a DCS Redis instance through Redis Desktop Manager over the intranet .. note:: 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 7e4dd47..cb8b24e 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 @@ -36,7 +36,6 @@ In addition, you must configure correct rules for the security groups of both th .. figure:: /_static/images/en-us_image_0277697231.png :alt: **Figure 1** Security group rules allowing the ECS to access the DCS instance - **Figure 1** Security group rules allowing the ECS to access the DCS instance #. Configuring security group for the DCS instance. @@ -47,7 +46,6 @@ In addition, you must configure correct rules for the security groups of both th .. figure:: /_static/images/en-us_image_0277697263.png :alt: **Figure 2** Security group rules making the DCS instance accessible to the ECS - **Figure 2** Security group rules making the DCS instance accessible to the ECS .. important:: diff --git a/umn/source/faqs/client_and_network_connection/what_if_err_unsupported_config_subcommand_is_displayed_in_springcloud.rst b/umn/source/faqs/client_and_network_connection/what_if_err_unsupported_config_subcommand_is_displayed_in_springcloud.rst index 6aba000..722fbfd 100644 --- a/umn/source/faqs/client_and_network_connection/what_if_err_unsupported_config_subcommand_is_displayed_in_springcloud.rst +++ b/umn/source/faqs/client_and_network_connection/what_if_err_unsupported_config_subcommand_is_displayed_in_springcloud.rst @@ -11,7 +11,6 @@ By using DCS Redis instances, Spring Session can implement session sharing. When .. figure:: /_static/images/en-us_image_0266315619.png :alt: **Figure 1** Spring Cloud error information - **Figure 1** Spring Cloud error information For security purposes, DCS does not support the **CONFIG** command initiated by a client. You need to perform the following steps: diff --git a/umn/source/faqs/redis_usage/does_dcs_for_redis_support_multiple_databases.rst b/umn/source/faqs/redis_usage/does_dcs_for_redis_support_multiple_databases.rst index 6ebf8ea..ac527c4 100644 --- a/umn/source/faqs/redis_usage/does_dcs_for_redis_support_multiple_databases.rst +++ b/umn/source/faqs/redis_usage/does_dcs_for_redis_support_multiple_databases.rst @@ -5,6 +5,6 @@ Does DCS for Redis Support Multiple Databases? ============================================== -Both single-node and master/standby DCS Redis instances support multiple databases. By default, single-node and master/standby DCS instances can read and write data in 256 databases (databases numbering 0–255). +Both single-node and master/standby DCS Redis instances support multiple databases. By default, single-node and master/standby DCS instances can read and write data in 256 databases (databases numbering 0-255). Cluster DCS instances do not support data read/write in multiple databases. diff --git a/umn/source/getting_started/accessing_an_instance/access_in_different_languages/c#.rst b/umn/source/getting_started/accessing_an_instance/access_in_different_languages/c#.rst index 67f6f37..fbe15a5 100644 --- a/umn/source/getting_started/accessing_an_instance/access_in_different_languages/c#.rst +++ b/umn/source/getting_started/accessing_an_instance/access_in_different_languages/c#.rst @@ -42,7 +42,6 @@ Procedure .. figure:: /_static/images/en-us_image_0148195318.png :alt: **Figure 1** Accessing the NuGet package manager console - **Figure 1** Accessing the NuGet package manager console #. Write the following code, and use the String Set and Get methods to test the connection. @@ -91,7 +90,7 @@ Procedure } } - *10.10.38.233:6379* contains an example IP address/domain name and port number of the DCS Redis instance. For details about how to obtain the IP address/domain name and port, see :ref:`1 `. Change the IP address/domain name and port as required. *\*******\** indicates the password used for logging in to the chosen DCS Redis instance. This password is defined during DCS Redis instance creation. + *10.10.38.233:6379* contains an example IP address/domain name and port number of the DCS Redis instance. For details about how to obtain the IP address/domain name and port, see :ref:`1 `. Change the IP address/domain name and port as required. ``********`` indicates the password used for logging in to the chosen DCS Redis instance. This password is defined during DCS Redis instance creation. #. Run the code. You have successfully accessed the instance if the following command output is displayed: 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 e626bed..04c718f 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 @@ -66,7 +66,6 @@ Procedure .. figure:: /_static/images/en-us_image_0000001188005622.png :alt: **Figure 1** Running the python command - **Figure 1** Running the python command b. Use the redis-py client to connect to the instance. In the following steps, commands are executed in CLI mode. (Alternatively, write the commands into a Python script and then execute the script.) @@ -77,7 +76,6 @@ Procedure .. figure:: /_static/images/en-us_image_0000001187846598.png :alt: **Figure 2** Entering the CLI mode - **Figure 2** Entering the CLI mode #. Run the following command to access the chosen DCS Redis instance: @@ -86,7 +84,7 @@ Procedure r = redis.StrictRedis(host='XXX.XXX.XXX.XXX', port=6379, password='******'); - *XXX.XXX.XXX.XXX* indicates the IP address/domain name of the DCS instance and **6379** is an example port number of the instance. For details about how to obtain the IP address/domain name and port, see :ref:`1 `. Change the IP address/domain name and port as required. *\*****\** indicates the password used for logging in to the chosen DCS Redis instance. This password is defined during DCS Redis instance creation. + *XXX.XXX.XXX.XXX* indicates the IP address/domain name of the DCS instance and **6379** is an example port number of the instance. For details about how to obtain the IP address/domain name and port, see :ref:`1 `. Change the IP address/domain name and port as required. ``******`` indicates the password used for logging in to the chosen DCS Redis instance. This password is defined during DCS Redis instance creation. You have successfully accessed the instance if the following command output is displayed. Enter commands to perform read and write operations on the database. @@ -94,7 +92,6 @@ Procedure .. figure:: /_static/images/en-us_image_0000001233126245.png :alt: **Figure 3** Redis connected successfully - **Figure 3** Redis connected successfully - If the instance is a Redis Cluster instance: diff --git a/umn/source/getting_started/accessing_an_instance/access_in_different_languages/go-redis.rst b/umn/source/getting_started/accessing_an_instance/access_in_different_languages/go-redis.rst index 85c4882..47db697 100644 --- a/umn/source/getting_started/accessing_an_instance/access_in_different_languages/go-redis.rst +++ b/umn/source/getting_started/accessing_an_instance/access_in_different_languages/go-redis.rst @@ -77,7 +77,7 @@ Procedure fmt.Println(val1) } - *host:port* are the IP address/domain name and port number of the DCS Redis instance. For details about how to obtain the IP address/domain name and port, see :ref:`1 `. Change the IP address/domain name and port as required. *\*******\** indicates the password used to log in to the DCS Redis instance. This password is defined during DCS Redis instance creation. + *host:port* are the IP address/domain name and port number of the DCS Redis instance. For details about how to obtain the IP address/domain name and port, see :ref:`1 `. Change the IP address/domain name and port as required. ``********`` indicates the password used to log in to the DCS Redis instance. This password is defined during DCS Redis instance creation. #. Run the **go build -o test main.go** command to package the code into an executable file, for example, **test**. diff --git a/umn/source/getting_started/accessing_an_instance/access_in_different_languages/node.js.rst b/umn/source/getting_started/accessing_an_instance/access_in_different_languages/node.js.rst index 1efa8b1..cf807ab 100644 --- a/umn/source/getting_started/accessing_an_instance/access_in_different_languages/node.js.rst +++ b/umn/source/getting_started/accessing_an_instance/access_in_different_languages/node.js.rst @@ -89,7 +89,7 @@ Procedure // All arguments are passed directly to the redis server: redis.set('key', 100, 'EX', 10); - *host* indicates the example IP address/domain name of DCS instance and *port* indicates the port number of DCS instance. For details about how to obtain the IP address/domain name and port, see :ref:`1 `. Change the IP address/domain name and port as required. *\*****\** indicates the password used for logging in to the chosen DCS Redis instance. This password is defined during DCS Redis instance creation. + *host* indicates the example IP address/domain name of DCS instance and *port* indicates the port number of DCS instance. For details about how to obtain the IP address/domain name and port, see :ref:`1 `. Change the IP address/domain name and port as required. ``******`` indicates the password used for logging in to the chosen DCS Redis instance. This password is defined during DCS Redis instance creation. #. Run the sample script to access the chosen DCS instance. @@ -163,7 +163,7 @@ Procedure // All arguments are passed directly to the redis server: redis.set('key', 100, 'EX', 10); - *host* indicates the example IP address/domain name of DCS instance and *port* indicates the port number of DCS instance. For details about how to obtain the IP address/domain name and port, see :ref:`1 `. Change the IP address/domain name and port as required. *\*****\** indicates the password used for logging in to the chosen DCS Redis instance. This password is defined during DCS Redis instance creation. + *host* indicates the example IP address/domain name of DCS instance and *port* indicates the port number of DCS instance. For details about how to obtain the IP address/domain name and port, see :ref:`1 `. Change the IP address/domain name and port as required. ``******`` indicates the password used for logging in to the chosen DCS Redis instance. This password is defined during DCS Redis instance creation. #. Run the sample script to access the chosen DCS instance. 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 7a63c67..90cc2e7 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 @@ -92,7 +92,7 @@ Creating a DCS Redis Instance - Lowercase letters - Uppercase letters - Digits - - special characters (:literal:`\`~!@#$^&*()-_=+\|{}:,<.>/?`) + - special characters (:literal:`\`~!@#$^&*()-_=+\\|{}:,<.>/?`) #. Click **More Settings** to display more configurations, including auto backup. diff --git a/umn/source/monitoring/configuring_alarm_rules_for_critical_metrics.rst b/umn/source/monitoring/configuring_alarm_rules_for_critical_metrics.rst index 0646739..7e74b78 100644 --- a/umn/source/monitoring/configuring_alarm_rules_for_critical_metrics.rst +++ b/umn/source/monitoring/configuring_alarm_rules_for_critical_metrics.rst @@ -15,25 +15,25 @@ Alarm Policies for DCS Redis Instances +-------------------+--------------+-----------------------------------------------+----------------------+------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+ | Metric | Normal Range | Alarm Policy | Approach Upper Limit | Handling Suggestion | +===================+==============+===============================================+======================+==============================================================================================================================================================================+ - | CPU Usage | 0–100 | Alarm threshold: 70 | No | Consider capacity expansion based on the service analysis. | + | CPU Usage | 0-100 | Alarm threshold: 70 | No | Consider capacity expansion based on the service analysis. | | | | | | | | | | Number of consecutive periods: 2 | | The CPU capacity of a single-node or master/standby instance cannot be expanded. If you need larger capacity, use a cluster instance instead. | | | | | | | | | | Alarm severity: Major | | | +-------------------+--------------+-----------------------------------------------+----------------------+------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+ - | Memory Usage | 0–100 | Alarm threshold: 70 | No | Expand the capacity of the instance. | + | Memory Usage | 0-100 | Alarm threshold: 70 | No | Expand the capacity of the instance. | | | | | | | | | | Number of consecutive periods: 2 | | | | | | | | | | | | Alarm severity: Major | | | +-------------------+--------------+-----------------------------------------------+----------------------+------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+ - | Connected Clients | 0–10,000 | Alarm threshold: 8000 | No | Optimize the connection pool in the service code to prevent the number of connections from exceeding the maximum limit. | + | Connected Clients | 0-10,000 | Alarm threshold: 8000 | No | Optimize the connection pool in the service code to prevent the number of connections from exceeding the maximum limit. | | | | | | | | | | Number of consecutive periods: 2 | | For single-node and master/standby instances, the maximum number of connections allowed is 10,000. You can adjust the threshold based on service requirements. | | | | | | | | | | Alarm severity: Major | | | +-------------------+--------------+-----------------------------------------------+----------------------+------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+ - | New Connections | 0–10,000 | Alarm threshold: 10,000 | - | Check whether **connect** is used and whether the client connection is abnormal. Use persistent connections ("pconnect" in Redis terminology) to ensure performance. | + | New Connections | 0-10,000 | Alarm threshold: 10,000 | - | Check whether **connect** is used and whether the client connection is abnormal. Use persistent connections ("pconnect" in Redis terminology) to ensure performance. | | | | | | | | (Count/min) | | Number of consecutive periods: 2 | | | | | | | | | @@ -69,7 +69,6 @@ In the following example, an alarm rule is set for the **CPU Usage** metric. .. figure:: /_static/images/en-us_image_0270432745.png :alt: **Figure 1** Viewing instance metrics - **Figure 1** Viewing instance metrics #. Locate the **CPU Usage** metric. Hover over the metric and click |image2| to create an alarm rule for the metric. @@ -86,7 +85,6 @@ In the following example, an alarm rule is set for the **CPU Usage** metric. .. figure:: /_static/images/en-us_image_0000001321666164.png :alt: **Figure 2** Setting the alarm content - **Figure 2** Setting the alarm content b. Set the alarm notification configurations. If you enable **Alarm Notification**, set the validity period, notification object, and trigger condition. diff --git a/umn/source/monitoring/dcs_metrics.rst b/umn/source/monitoring/dcs_metrics.rst index bed8ea3..cff0099 100644 --- a/umn/source/monitoring/dcs_metrics.rst +++ b/umn/source/monitoring/dcs_metrics.rst @@ -43,7 +43,7 @@ DCS Redis 3.0 Instance Metrics +----------------------------+----------------------------+----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+---------------+------------------------------------------------------------+------------------------------+ | 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% | Monitored object: | 1 minute | | | | | | | | | | | Unit: % | | Single-node, master/standby, or cluster DCS Redis instance | | | | | | | | | @@ -51,7 +51,7 @@ DCS Redis 3.0 Instance Metrics | | | | | | | | | | | | 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% | Monitored object: | 1 minute | | | | | | | | | | | Unit: % | | Single-node, master/standby, or cluster DCS Redis instance | | | | | | | | | @@ -59,7 +59,7 @@ DCS Redis 3.0 Instance Metrics | | | | | | | | | | | | dcs_instance_id | | +----------------------------+----------------------------+----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+---------------+------------------------------------------------------------+------------------------------+ - | 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 | Monitored object: | 1 minute | | | | | | | | | | | Unit: byte/s | | Single-node, master/standby, or cluster DCS Redis instance | | | | | | | | | @@ -67,7 +67,7 @@ DCS Redis 3.0 Instance Metrics | | | | | | | | | | | | dcs_instance_id | | +----------------------------+----------------------------+----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+---------------+------------------------------------------------------------+------------------------------+ - | 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 | Monitored object: | 1 minute | | | | | | | | | | | Unit: byte/s | | Single-node, master/standby, or cluster DCS Redis instance | | | | | | | | | @@ -83,7 +83,7 @@ DCS Redis 3.0 Instance Metrics | | | | | | | | | | | | dcs_instance_id | | +----------------------------+----------------------------+----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+---------------+------------------------------------------------------------+------------------------------+ - | connected_clients | Connected Clients | Number of connected clients (excluding those from slave nodes) | ≥ 0 | Monitored object: | 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 | | | | | | | | | @@ -91,7 +91,7 @@ DCS Redis 3.0 Instance Metrics | | | | | | | | | | | | dcs_instance_id | | +----------------------------+----------------------------+----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+---------------+------------------------------------------------------------+------------------------------+ - | client_longest_out_list | Client Longest Output List | Longest output list among current client connections | ≥ 0 | Monitored object: | 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 | | | | | | | | | @@ -99,7 +99,7 @@ DCS Redis 3.0 Instance Metrics | | | | | | | | | | | | dcs_instance_id | | +----------------------------+----------------------------+----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+---------------+------------------------------------------------------------+------------------------------+ - | 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 | Monitored object: | 1 minute | | | | | | | | | | | Unit: byte | | Single-node, master/standby, or cluster DCS Redis instance | | | | | | | | | @@ -107,7 +107,7 @@ DCS Redis 3.0 Instance Metrics | | | | | | | | | | | | dcs_instance_id | | +----------------------------+----------------------------+----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+---------------+------------------------------------------------------------+------------------------------+ - | blocked_clients | Blocked Clients | Number of clients suspended by block operations such as BLPOP, BRPOP, and BRPOPLPUSH | ≥ 0 | Monitored object: | 1 minute | + | 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 | | | | | | | | | @@ -115,7 +115,7 @@ DCS Redis 3.0 Instance Metrics | | | | | | | | | | | | dcs_instance_id | | +----------------------------+----------------------------+----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+---------------+------------------------------------------------------------+------------------------------+ - | 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 | Monitored object: | 1 minute | | | | | | | | | | | Unit: byte | | Single-node, master/standby, or cluster DCS Redis instance | | | | | | | | | @@ -123,7 +123,7 @@ DCS Redis 3.0 Instance Metrics | | | | | | | | | | | | dcs_instance_id | | +----------------------------+----------------------------+----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+---------------+------------------------------------------------------------+------------------------------+ - | 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 | Monitored object: | 1 minute | | | | | | | | | | | Unit: byte | | Single-node, master/standby, or cluster DCS Redis instance | | | | | | | | | @@ -131,7 +131,7 @@ DCS Redis 3.0 Instance Metrics | | | | | | | | | | | | dcs_instance_id | | +----------------------------+----------------------------+----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+---------------+------------------------------------------------------------+------------------------------+ - | 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 | Monitored object: | 1 minute | | | | | | | | | | | Unit: byte | | Single-node, master/standby, or cluster DCS Redis instance | | | | | | | | | @@ -139,7 +139,7 @@ DCS Redis 3.0 Instance Metrics | | | | | | | | | | | | dcs_instance_id | | +----------------------------+----------------------------+----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+---------------+------------------------------------------------------------+------------------------------+ - | 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 | Monitored object: | 1 minute | | | | | | | | | | | Unit: byte | | Single-node, master/standby, or cluster DCS Redis instance | | | | | | | | | @@ -147,7 +147,7 @@ DCS Redis 3.0 Instance Metrics | | | | | | | | | | | | dcs_instance_id | | +----------------------------+----------------------------+----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+---------------+------------------------------------------------------------+------------------------------+ - | memory_frag_ratio | Memory Fragmentation Ratio | Current memory fragmentation, which is the ratio between **used_memory_rss**/**used_memory**. | ≥ 0 | Monitored object: | 1 minute | + | 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 | | | | | | | | | @@ -155,7 +155,7 @@ DCS Redis 3.0 Instance Metrics | | | | | | | | | | | | dcs_instance_id | | +----------------------------+----------------------------+----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+---------------+------------------------------------------------------------+------------------------------+ - | total_connections_received | New Connections | Number of connections received during the monitoring period | ≥ 0 | Monitored object: | 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 | | | | | | | | | @@ -163,7 +163,7 @@ DCS Redis 3.0 Instance Metrics | | | | | | | | | | | | dcs_instance_id | | +----------------------------+----------------------------+----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+---------------+------------------------------------------------------------+------------------------------+ - | total_commands_processed | Commands Processed | Number of commands processed during the monitoring period | ≥ 0 | Monitored object: | 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 | | | | | | | | | @@ -171,7 +171,7 @@ DCS Redis 3.0 Instance Metrics | | | | | | | | | | | | dcs_instance_id | | +----------------------------+----------------------------+----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+---------------+------------------------------------------------------------+------------------------------+ - | instantaneous_ops | Ops per Second | Number of commands processed per second | ≥ 0 | Monitored object: | 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 | | | | | | | | | @@ -179,7 +179,7 @@ DCS Redis 3.0 Instance Metrics | | | | | | | | | | | | dcs_instance_id | | +----------------------------+----------------------------+----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+---------------+------------------------------------------------------------+------------------------------+ - | 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 | Monitored object: | 1 minute | | | | | | | | | | | Unit: byte | | Single-node, master/standby, or cluster DCS Redis instance | | | | | | | | | @@ -187,7 +187,7 @@ DCS Redis 3.0 Instance Metrics | | | | | | | | | | | | dcs_instance_id | | +----------------------------+----------------------------+----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+---------------+------------------------------------------------------------+------------------------------+ - | 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 | Monitored object: | 1 minute | | | | | | | | | | | Unit: byte | | Single-node, master/standby, or cluster DCS Redis instance | | | | | | | | | @@ -195,7 +195,7 @@ DCS Redis 3.0 Instance Metrics | | | | | | | | | | | | dcs_instance_id | | +----------------------------+----------------------------+----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+---------------+------------------------------------------------------------+------------------------------+ - | 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 | Monitored object: | 1 minute | | | | | | | | | | | Unit: kbit/s | | Single-node, master/standby, or cluster DCS Redis instance | | | | | | | | | @@ -203,7 +203,7 @@ DCS Redis 3.0 Instance Metrics | | | | | | | | | | | | dcs_instance_id | | +----------------------------+----------------------------+----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+---------------+------------------------------------------------------------+------------------------------+ - | 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 | Monitored object: | 1 minute | | | | | | | | | | | Unit: kbit/s | | Single-node, master/standby, or cluster DCS Redis instance | | | | | | | | | @@ -211,7 +211,7 @@ DCS Redis 3.0 Instance Metrics | | | | | | | | | | | | dcs_instance_id | | +----------------------------+----------------------------+----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+---------------+------------------------------------------------------------+------------------------------+ - | rejected_connections | Rejected Connections | Number of connections that have exceeded maxclients and been rejected during the monitoring period | ≥ 0 | Monitored object: | 1 minute | + | 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 | | | | | | | | | @@ -219,7 +219,7 @@ DCS Redis 3.0 Instance Metrics | | | | | | | | | | | | dcs_instance_id | | +----------------------------+----------------------------+----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+---------------+------------------------------------------------------------+------------------------------+ - | expired_keys | Expired Keys | Number of keys that have expired and been deleted during the monitoring period | ≥ 0 | Monitored object: | 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 | | | | | | | | | @@ -227,7 +227,7 @@ DCS Redis 3.0 Instance Metrics | | | | | | | | | | | | dcs_instance_id | | +----------------------------+----------------------------+----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+---------------+------------------------------------------------------------+------------------------------+ - | evicted_keys | Evicted Keys | Number of keys that have been evicted and deleted during the monitoring period | ≥ 0 | Monitored object: | 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 | | | | | | | | | @@ -235,7 +235,7 @@ DCS Redis 3.0 Instance Metrics | | | | | | | | | | | | dcs_instance_id | | +----------------------------+----------------------------+----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+---------------+------------------------------------------------------------+------------------------------+ - | keyspace_hits | Keyspace Hits | Number of successful lookups of keys in the main dictionary during the monitoring period | ≥ 0 | Monitored object: | 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 | | | | | | | | | @@ -243,7 +243,7 @@ DCS Redis 3.0 Instance Metrics | | | | | | | | | | | | dcs_instance_id | | +----------------------------+----------------------------+----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+---------------+------------------------------------------------------------+------------------------------+ - | keyspace_misses | Keyspace Misses | Number of failed lookups of keys in the main dictionary during the monitoring period | ≥ 0 | Monitored object: | 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 | | | | | | | | | @@ -251,7 +251,7 @@ DCS Redis 3.0 Instance Metrics | | | | | | | | | | | | dcs_instance_id | | +----------------------------+----------------------------+----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+---------------+------------------------------------------------------------+------------------------------+ - | pubsub_channels | PubSub Channels | Number of Pub/Sub channels | ≥ 0 | Monitored object: | 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 | | | | | | | | | @@ -259,7 +259,7 @@ DCS Redis 3.0 Instance Metrics | | | | | | | | | | | | dcs_instance_id | | +----------------------------+----------------------------+----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+---------------+------------------------------------------------------------+------------------------------+ - | pubsub_patterns | PubSub Patterns | Number of Pub/Sub patterns | ≥ 0 | Monitored object: | 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 | | | | | | | | | @@ -267,7 +267,7 @@ DCS Redis 3.0 Instance Metrics | | | | | | | | | | | | dcs_instance_id | | +----------------------------+----------------------------+----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+---------------+------------------------------------------------------------+------------------------------+ - | 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% | Monitored object: | 1 minute | | | | | | | | | | | Unit: % | | Single-node, master/standby, or cluster DCS Redis instance | | | | | | | | | @@ -275,7 +275,7 @@ DCS Redis 3.0 Instance Metrics | | | | | | | | | | | | dcs_instance_id | | +----------------------------+----------------------------+----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+---------------+------------------------------------------------------------+------------------------------+ - | 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 | Monitored object: | 1 minute | | | | | | | | | | | Unit: ms | | Single-node, master/standby, or cluster DCS Redis instance | | | | | | | | | @@ -283,7 +283,7 @@ DCS Redis 3.0 Instance Metrics | | | | | | | | | | | | dcs_instance_id | | +----------------------------+----------------------------+----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+---------------+------------------------------------------------------------+------------------------------+ - | auth_errors | Authentication Failures | Number of failed authentications | ≥ 0 | Monitored object: | 1 minute | + | auth_errors | Authentication Failures | Number of failed authentications | >= 0 | Monitored object: | 1 minute | | | | | | | | | | | | | Single-node or master/standby DCS Redis instance | | | | | | | | | @@ -299,7 +299,7 @@ DCS Redis 3.0 Instance Metrics | | | | | | | | | | | | dcs_instance_id | | +----------------------------+----------------------------+----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+---------------+------------------------------------------------------------+------------------------------+ - | keys | Keys | Number of keys in Redis | ≥ 0 | Monitored object: | 1 minute | + | keys | Keys | Number of keys in Redis | >= 0 | Monitored object: | 1 minute | | | | | | | | | | | | | Single-node or master/standby DCS Redis instance | | | | | | | | | @@ -320,7 +320,7 @@ DCS Redis 4.0 and 5.0 Instance Metrics +----------------------------+----------------------------+----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+---------------+------------------------------------------------------------+------------------------------+ | 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% | Monitored object: | 1 minute | | | | | | | | | | | Unit: % | | Single-node or master/standby DCS Redis instance | | | | | | | | | @@ -328,7 +328,7 @@ DCS Redis 4.0 and 5.0 Instance Metrics | | | | | | | | | | | | dcs_instance_id | | +----------------------------+----------------------------+----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+---------------+------------------------------------------------------------+------------------------------+ - | 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 | Monitored object: | 1 minute | | | | | | | | | | | Unit: ms | | Single-node, master/standby, or cluster DCS Redis instance | | | | | | | | | @@ -336,7 +336,7 @@ DCS Redis 4.0 and 5.0 Instance Metrics | | | | | | | | | | | | dcs_instance_id | | +----------------------------+----------------------------+----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+---------------+------------------------------------------------------------+------------------------------+ - | total_connections_received | New Connections | Number of connections received during the monitoring period | ≥ 0 | Monitored object: | 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 | | | | | | | | | @@ -352,7 +352,7 @@ DCS Redis 4.0 and 5.0 Instance Metrics | | | | | | | | | | | | 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% | Monitored object: | 1 minute | | | | | | | | | | | Unit: % | | Single-node, master/standby, or cluster DCS Redis instance | | | | | | | | | @@ -360,7 +360,7 @@ DCS Redis 4.0 and 5.0 Instance Metrics | | | | | | | | | | | | dcs_instance_id | | +----------------------------+----------------------------+----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+---------------+------------------------------------------------------------+------------------------------+ - | expires | Keys With an Expiration | Number of keys with an expiration in Redis | ≥ 0 | Monitored object: | 1 minute | + | 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 | | | | | | | | | @@ -368,7 +368,7 @@ DCS Redis 4.0 and 5.0 Instance Metrics | | | | | | | | | | | | dcs_instance_id | | +----------------------------+----------------------------+----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+---------------+------------------------------------------------------------+------------------------------+ - | 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% | Monitored object: | 1 minute | | | | | | | | | | | Unit: % | | Single-node, master/standby, or cluster DCS Redis instance | | | | | | | | | @@ -376,7 +376,7 @@ DCS Redis 4.0 and 5.0 Instance Metrics | | | | | | | | | | | | dcs_instance_id | | +----------------------------+----------------------------+----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+---------------+------------------------------------------------------------+------------------------------+ - | 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 | Monitored object: | 1 minute | | | | | | | | | | | Unit: byte | | Single-node, master/standby, or cluster DCS Redis instance | | | | | | | | | @@ -384,7 +384,7 @@ DCS Redis 4.0 and 5.0 Instance Metrics | | | | | | | | | | | | dcs_instance_id | | +----------------------------+----------------------------+----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+---------------+------------------------------------------------------------+------------------------------+ - | 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 | Monitored object: | 1 minute | | | | | | | | | | | Unit: byte | | Single-node, master/standby, or cluster DCS Redis instance | | | | | | | | | @@ -392,7 +392,7 @@ DCS Redis 4.0 and 5.0 Instance Metrics | | | | | | | | | | | | dcs_instance_id | | +----------------------------+----------------------------+----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+---------------+------------------------------------------------------------+------------------------------+ - | 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% | Monitored object: | 1 minute | | | | | | | | | | | Unit: % | | Single-node, master/standby, or cluster DCS Redis instance | | | | | | | | | @@ -400,7 +400,7 @@ DCS Redis 4.0 and 5.0 Instance Metrics | | | | | | | | | | | | dcs_instance_id | | +----------------------------+----------------------------+----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+---------------+------------------------------------------------------------+------------------------------+ - | 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 | Monitored object: | 1 minute | | | | | | | | | | | Unit: byte | | Single-node, master/standby, or cluster DCS Redis instance | | | | | | | | | @@ -408,7 +408,7 @@ DCS Redis 4.0 and 5.0 Instance Metrics | | | | | | | | | | | | dcs_instance_id | | +----------------------------+----------------------------+----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+---------------+------------------------------------------------------------+------------------------------+ - | instantaneous_ops | Ops per Second | Number of commands processed per second | ≥ 0 | Monitored object: | 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 | | | | | | | | | @@ -416,7 +416,7 @@ DCS Redis 4.0 and 5.0 Instance Metrics | | | | | | | | | | | | dcs_instance_id | | +----------------------------+----------------------------+----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+---------------+------------------------------------------------------------+------------------------------+ - | keyspace_misses | Keyspace Misses | Number of failed lookups of keys in the main dictionary during the monitoring period | ≥ 0 | Monitored object: | 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 | | | | | | | | | @@ -424,7 +424,7 @@ DCS Redis 4.0 and 5.0 Instance Metrics | | | | | | | | | | | | dcs_instance_id | | +----------------------------+----------------------------+----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+---------------+------------------------------------------------------------+------------------------------+ - | keys | Keys | Number of keys in Redis | ≥ 0 | Monitored object: | 1 minute | + | keys | Keys | Number of keys in Redis | >= 0 | Monitored object: | 1 minute | | | | | | | | | | | | | Single-node, master/standby, or cluster DCS Redis instance | | | | | | | | | @@ -432,7 +432,7 @@ DCS Redis 4.0 and 5.0 Instance Metrics | | | | | | | | | | | | dcs_instance_id | | +----------------------------+----------------------------+----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+---------------+------------------------------------------------------------+------------------------------+ - | 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 | Monitored object: | 1 minute | | | | | | | | | | | Unit: count/s | | Single-node, master/standby, or cluster DCS Redis instance | | | | | | | | | @@ -440,7 +440,7 @@ DCS Redis 4.0 and 5.0 Instance Metrics | | | | | | | | | | | | dcs_instance_id | | +----------------------------+----------------------------+----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+---------------+------------------------------------------------------------+------------------------------+ - | 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 | Monitored object: | 1 minute | | | | | | | | | | | Unit: % | | Single-node, master/standby, or cluster DCS Redis instance | | | | | | | | | @@ -448,7 +448,7 @@ DCS Redis 4.0 and 5.0 Instance Metrics | | | | | | | | | | | | dcs_instance_id | | +----------------------------+----------------------------+----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+---------------+------------------------------------------------------------+------------------------------+ - | 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 | Monitored object: | 1 minute | | | | | | | | | | | Unit: % | | Single-node, master/standby, or cluster DCS Redis instance | | | | | | | | | @@ -464,7 +464,7 @@ DCS Redis 4.0 and 5.0 Instance Metrics | | | | | | | | | | | | dcs_instance_id | | +----------------------------+----------------------------+----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+---------------+------------------------------------------------------------+------------------------------+ - | 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 | Monitored object: | 1 minute | | | | | | | | | | | Unit: μs | | Single-node, master/standby, or cluster DCS Redis instance | | | | | | | | | @@ -472,7 +472,7 @@ DCS Redis 4.0 and 5.0 Instance Metrics | | | | | | | | | | | | dcs_instance_id | | +----------------------------+----------------------------+----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+---------------+------------------------------------------------------------+------------------------------+ - | 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 | Monitored object: | 1 minute | | | | | | | | | | | Unit: μs | | Single-node, master/standby, or cluster DCS Redis instance | | | | | | | | | @@ -480,7 +480,7 @@ DCS Redis 4.0 and 5.0 Instance Metrics | | | | | | | | | | | | dcs_instance_id | | +----------------------------+----------------------------+----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+---------------+------------------------------------------------------------+------------------------------+ - | 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 | Monitored object: | 1 minute | | | | | | | | | | | Unit: % | | Single-node, master/standby, or cluster DCS Redis instance | | | | | | | | | @@ -488,7 +488,7 @@ DCS Redis 4.0 and 5.0 Instance Metrics | | | | | | | | | | | | dcs_instance_id | | +----------------------------+----------------------------+----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+---------------+------------------------------------------------------------+------------------------------+ - | blocked_clients | Blocked Clients | Number of clients suspended by block operations | ≥ 0 | Monitored object: | 1 minute | + | 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 | | | | | | | | | @@ -496,7 +496,7 @@ DCS Redis 4.0 and 5.0 Instance Metrics | | | | | | | | | | | | dcs_instance_id | | +----------------------------+----------------------------+----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+---------------+------------------------------------------------------------+------------------------------+ - | connected_clients | Connected Clients | Number of connected clients (excluding those from slave nodes) | ≥ 0 | Monitored object: | 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 | | | | | | | | | @@ -504,7 +504,7 @@ DCS Redis 4.0 and 5.0 Instance Metrics | | | | | | | | | | | | dcs_instance_id | | +----------------------------+----------------------------+----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+---------------+------------------------------------------------------------+------------------------------+ - | 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 | Monitored object: | 1 minute | | | | | | | | | | | Unit: count/s | | Single-node, master/standby, or cluster DCS Redis instance | | | | | | | | | @@ -512,7 +512,7 @@ DCS Redis 4.0 and 5.0 Instance Metrics | | | | | | | | | | | | dcs_instance_id | | +----------------------------+----------------------------+----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+---------------+------------------------------------------------------------+------------------------------+ - | evicted_keys | Evicted Keys | Number of keys that have been evicted and deleted during the monitoring period | ≥ 0 | Monitored object: | 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 | | | | | | | | | @@ -520,7 +520,7 @@ DCS Redis 4.0 and 5.0 Instance Metrics | | | | | | | | | | | | dcs_instance_id | | +----------------------------+----------------------------+----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+---------------+------------------------------------------------------------+------------------------------+ - | 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 | Monitored object: | 1 minute | | | | | | | | | | | Unit: count/s | | Single-node, master/standby, or cluster DCS Redis instance | | | | | | | | | @@ -528,7 +528,7 @@ DCS Redis 4.0 and 5.0 Instance Metrics | | | | | | | | | | | | dcs_instance_id | | +----------------------------+----------------------------+----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+---------------+------------------------------------------------------------+------------------------------+ - | expired_keys | Expired Keys | Number of keys that have expired and been deleted during the monitoring period | ≥ 0 | Monitored object: | 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 | | | | | | | | | @@ -536,7 +536,7 @@ DCS Redis 4.0 and 5.0 Instance Metrics | | | | | | | | | | | | dcs_instance_id | | +----------------------------+----------------------------+----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+---------------+------------------------------------------------------------+------------------------------+ - | 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 | Monitored object: | 1 minute | | | | | | | | | | | Unit: count/s | | Single-node, master/standby, or cluster DCS Redis instance | | | | | | | | | @@ -544,7 +544,7 @@ DCS Redis 4.0 and 5.0 Instance Metrics | | | | | | | | | | | | dcs_instance_id | | +----------------------------+----------------------------+----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+---------------+------------------------------------------------------------+------------------------------+ - | 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 | Monitored object: | 1 minute | | | | | | | | | | | Unit: count/s | | Single-node, master/standby, or cluster DCS Redis instance | | | | | | | | | @@ -552,7 +552,7 @@ DCS Redis 4.0 and 5.0 Instance Metrics | | | | | | | | | | | | dcs_instance_id | | +----------------------------+----------------------------+----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+---------------+------------------------------------------------------------+------------------------------+ - | 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 | Monitored object: | 1 minute | | | | | | | | | | | Unit: count/s | | Single-node, master/standby, or cluster DCS Redis instance | | | | | | | | | @@ -560,7 +560,7 @@ DCS Redis 4.0 and 5.0 Instance Metrics | | | | | | | | | | | | dcs_instance_id | | +----------------------------+----------------------------+----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+---------------+------------------------------------------------------------+------------------------------+ - | 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 | Monitored object: | 1 minute | | | | | | | | | | | Unit: count/s | | Single-node, master/standby, or cluster DCS Redis instance | | | | | | | | | @@ -568,7 +568,7 @@ DCS Redis 4.0 and 5.0 Instance Metrics | | | | | | | | | | | | dcs_instance_id | | +----------------------------+----------------------------+----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+---------------+------------------------------------------------------------+------------------------------+ - | 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 | Monitored object: | 1 minute | | | | | | | | | | | Unit: count/s | | Single-node, master/standby, or cluster DCS Redis instance | | | | | | | | | @@ -576,7 +576,7 @@ DCS Redis 4.0 and 5.0 Instance Metrics | | | | | | | | | | | | dcs_instance_id | | +----------------------------+----------------------------+----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+---------------+------------------------------------------------------------+------------------------------+ - | 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 | Monitored object: | 1 minute | | | | | | | | | | | Unit: count/s | | Single-node, master/standby, or cluster DCS Redis instance | | | | | | | | | @@ -584,7 +584,7 @@ DCS Redis 4.0 and 5.0 Instance Metrics | | | | | | | | | | | | dcs_instance_id | | +----------------------------+----------------------------+----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+---------------+------------------------------------------------------------+------------------------------+ - | 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 | Monitored object: | 1 minute | | | | | | | | | | | Unit: KB/s | | Single-node, master/standby, or cluster DCS Redis instance | | | | | | | | | @@ -592,7 +592,7 @@ DCS Redis 4.0 and 5.0 Instance Metrics | | | | | | | | | | | | dcs_instance_id | | +----------------------------+----------------------------+----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+---------------+------------------------------------------------------------+------------------------------+ - | 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 | Monitored object: | 1 minute | | | | | | | | | | | Unit: KB/s | | Single-node, master/standby, or cluster DCS Redis instance | | | | | | | | | @@ -600,7 +600,7 @@ DCS Redis 4.0 and 5.0 Instance Metrics | | | | | | | | | | | | dcs_instance_id | | +----------------------------+----------------------------+----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+---------------+------------------------------------------------------------+------------------------------+ - | memory_frag_ratio | Memory Fragmentation Ratio | Ratio between Used Memory RSS and Used Memory | ≥ 0 | Monitored object: | 1 minute | + | 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 | | | | | | | | | @@ -608,7 +608,7 @@ DCS Redis 4.0 and 5.0 Instance Metrics | | | | | | | | | | | | dcs_instance_id | | +----------------------------+----------------------------+----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+---------------+------------------------------------------------------------+------------------------------+ - | 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 | Monitored object: | 1 minute | | | | | | | | | | | Unit: count/s | | Single-node, master/standby, or cluster DCS Redis instance | | | | | | | | | @@ -616,7 +616,7 @@ DCS Redis 4.0 and 5.0 Instance Metrics | | | | | | | | | | | | dcs_instance_id | | +----------------------------+----------------------------+----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+---------------+------------------------------------------------------------+------------------------------+ - | 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 | Monitored object: | 1 minute | | | | | | | | | | | Unit: count/s | | Single-node, master/standby, or cluster DCS Redis instance | | | | | | | | | @@ -624,7 +624,7 @@ DCS Redis 4.0 and 5.0 Instance Metrics | | | | | | | | | | | | dcs_instance_id | | +----------------------------+----------------------------+----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+---------------+------------------------------------------------------------+------------------------------+ - | pubsub_channels | PubSub Channels | Number of Pub/Sub channels | ≥ 0 | Monitored object: | 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 | | | | | | | | | @@ -632,7 +632,7 @@ DCS Redis 4.0 and 5.0 Instance Metrics | | | | | | | | | | | | dcs_instance_id | | +----------------------------+----------------------------+----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+---------------+------------------------------------------------------------+------------------------------+ - | pubsub_patterns | PubSub Patterns | Number of Pub/Sub patterns | ≥ 0 | Monitored object: | 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 | | | | | | | | | @@ -640,7 +640,7 @@ DCS Redis 4.0 and 5.0 Instance Metrics | | | | | | | | | | | | dcs_instance_id | | +----------------------------+----------------------------+----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+---------------+------------------------------------------------------------+------------------------------+ - | 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 | Monitored object: | 1 minute | | | | | | | | | | | Unit: count/s | | Single-node, master/standby, or cluster DCS Redis instance | | | | | | | | | @@ -648,7 +648,7 @@ DCS Redis 4.0 and 5.0 Instance Metrics | | | | | | | | | | | | dcs_instance_id | | +----------------------------+----------------------------+----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+---------------+------------------------------------------------------------+------------------------------+ - | 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 | Monitored object: | 1 minute | | | | | | | | | | | Unit: byte | | Single-node, master/standby, or cluster DCS Redis instance | | | | | | | | | @@ -656,7 +656,7 @@ DCS Redis 4.0 and 5.0 Instance Metrics | | | | | | | | | | | | dcs_instance_id | | +----------------------------+----------------------------+----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+---------------+------------------------------------------------------------+------------------------------+ - | 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 | Monitored object: | 1 minute | | | | | | | | | | | Unit: byte | | Single-node, master/standby, or cluster DCS Redis instance | | | | | | | | | @@ -664,7 +664,7 @@ DCS Redis 4.0 and 5.0 Instance Metrics | | | | | | | | | | | | dcs_instance_id | | +----------------------------+----------------------------+----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+---------------+------------------------------------------------------------+------------------------------+ - | 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 | Monitored object: | 1 minute | | | | | | | | | | | Unit: count/s | | Single-node, master/standby, or cluster DCS Redis instance | | | | | | | | | @@ -672,7 +672,7 @@ DCS Redis 4.0 and 5.0 Instance Metrics | | | | | | | | | | | | dcs_instance_id | | +----------------------------+----------------------------+----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+---------------+------------------------------------------------------------+------------------------------+ - | 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 | Monitored object: | 1 minute | | | | | | | | | | | Unit: count/s | | Single-node, master/standby, or cluster DCS Redis instance | | | | | | | | | @@ -680,7 +680,7 @@ DCS Redis 4.0 and 5.0 Instance Metrics | | | | | | | | | | | | dcs_instance_id | | +----------------------------+----------------------------+----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+---------------+------------------------------------------------------------+------------------------------+ - | 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 | Monitored object: | 1 minute | | | | | | | | | | | Unit: count | | Redis Cluster instance | | | | | | | | | @@ -688,7 +688,7 @@ DCS Redis 4.0 and 5.0 Instance Metrics | | | | | | | | | | | | dcs_instance_id | | +----------------------------+----------------------------+----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+---------------+------------------------------------------------------------+------------------------------+ - | bandwidth_usage | Bandwidth Usage | Percentage of the used bandwidth to the maximum bandwidth limit | 0–200% | Monitored object: | 1 minute | + | bandwidth_usage | Bandwidth Usage | Percentage of the used bandwidth to the maximum bandwidth limit | 0-200% | Monitored object: | 1 minute | | | | | | | | | | | | | Redis Cluster instance | | | | | | | | | @@ -696,7 +696,7 @@ DCS Redis 4.0 and 5.0 Instance Metrics | | | | | | | | | | | | dcs_instance_id | | +----------------------------+----------------------------+----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+---------------+------------------------------------------------------------+------------------------------+ - | keyspace_misses | Keyspace Misses | Number of failed lookups of keys in the main dictionary during the monitoring period | ≥ 0 | Monitored object: | 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 | | | | | | | | | @@ -704,7 +704,7 @@ DCS Redis 4.0 and 5.0 Instance Metrics | | | | | | | | | | | | dcs_instance_id | | +----------------------------+----------------------------+----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+---------------+------------------------------------------------------------+------------------------------+ - | 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 | Monitored object: | 1 minute | | | | | | | | | | | | | Single-node, master/standby, or cluster DCS Redis instance | | | | | | | | | @@ -712,7 +712,7 @@ DCS Redis 4.0 and 5.0 Instance Metrics | | | | | | | | | | | | dcs_instance_id | | +----------------------------+----------------------------+----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+---------------+------------------------------------------------------------+------------------------------+ - | used_memory_dataset_perc | Used Memory Dataset Ratio | Percentage of dataset memory that server has used | 0–100% | Monitored object: | 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 | | | | | | | | | @@ -737,7 +737,7 @@ Node Metrics of DCS Redis 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% | Monitored object: | 1 minute | | | | | | | | | | | Unit: % | | Redis Server of a cluster DCS Redis 3.0, 4.0, or 5.0 instance | | | | | | | | | @@ -747,7 +747,7 @@ Node Metrics of DCS Redis Instances | | | | | | | | | | | | dcs_cluster_redis_node | | +----------------------------+----------------------------+--------------------------------------------------------------------------------------------------------------------------------+---------------+---------------------------------------------------------------+------------------------------+ - | 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% | Monitored object: | 1 minute | | | | | | | | | | | Unit: % | | Redis Server of a cluster DCS Redis 3.0, 4.0, or 5.0 instance | | | | | | | | | @@ -755,7 +755,7 @@ Node Metrics of DCS Redis Instances | | | | | | | | | | | | dcs_cluster_redis_node | | +----------------------------+----------------------------+--------------------------------------------------------------------------------------------------------------------------------+---------------+---------------------------------------------------------------+------------------------------+ - | connected_clients | Connected Clients | Number of connected clients (excluding those from slave nodes) | ≥ 0 | Monitored object: | 1 minute | + | 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 | | | | | | | | | @@ -765,7 +765,7 @@ Node Metrics of DCS Redis Instances | | | | | | | | | | | | dcs_cluster_redis_node | | +----------------------------+----------------------------+--------------------------------------------------------------------------------------------------------------------------------+---------------+---------------------------------------------------------------+------------------------------+ - | client_longest_out_list | Client Longest Output List | Longest output list among current client connections | ≥ 0 | Monitored object: | 1 minute | + | 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 | | | | | | | | | @@ -775,7 +775,7 @@ Node Metrics of DCS Redis Instances | | | | | | | | | | | | 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 | + | 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 | | | | | | | | | @@ -785,7 +785,7 @@ Node Metrics of DCS Redis Instances | | | | | | | | | | | | 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 | + | 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 | | | | | | | | | @@ -795,7 +795,7 @@ Node Metrics of DCS Redis Instances | | | | | | | | | | | | dcs_cluster_redis_node | | +----------------------------+----------------------------+--------------------------------------------------------------------------------------------------------------------------------+---------------+---------------------------------------------------------------+------------------------------+ - | 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 | Monitored object: | 1 minute | | | | | | | | | | | Unit: byte | | Redis Server of a cluster DCS Redis 3.0, 4.0, or 5.0 instance | | | | | | | | | @@ -805,7 +805,7 @@ Node Metrics of DCS Redis Instances | | | | | | | | | | | | 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 | + | 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 | | | | | | | | | @@ -815,7 +815,7 @@ Node Metrics of DCS Redis Instances | | | | | | | | | | | | 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 | + | 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 | | | | | | | | | @@ -825,7 +825,7 @@ Node Metrics of DCS Redis Instances | | | | | | | | | | | | dcs_cluster_redis_node | | +----------------------------+----------------------------+--------------------------------------------------------------------------------------------------------------------------------+---------------+---------------------------------------------------------------+------------------------------+ - | 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 | Monitored object: | 1 minute | | | | | | | | | | | Unit: byte | | Redis Server of a cluster DCS Redis 3.0, 4.0, or 5.0 instance | | | | | | | | | @@ -835,7 +835,7 @@ Node Metrics of DCS Redis Instances | | | | | | | | | | | | 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 | + | 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 | | | | | | | | | @@ -845,7 +845,7 @@ Node Metrics of DCS Redis Instances | | | | | | | | | | | | dcs_cluster_redis_node | | +----------------------------+----------------------------+--------------------------------------------------------------------------------------------------------------------------------+---------------+---------------------------------------------------------------+------------------------------+ - | total_connections_received | New Connections | Number of connections received during the monitoring period | ≥ 0 | Monitored object: | 1 minute | + | 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 | | | | | | | | | @@ -855,7 +855,7 @@ Node Metrics of DCS Redis Instances | | | | | | | | | | | | dcs_cluster_redis_node | | +----------------------------+----------------------------+--------------------------------------------------------------------------------------------------------------------------------+---------------+---------------------------------------------------------------+------------------------------+ - | total_commands_processed | Commands Processed | Number of commands processed during the monitoring period | ≥ 0 | Monitored object: | 1 minute | + | 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 | | | | | | | | | @@ -865,7 +865,7 @@ Node Metrics of DCS Redis Instances | | | | | | | | | | | | dcs_cluster_redis_node | | +----------------------------+----------------------------+--------------------------------------------------------------------------------------------------------------------------------+---------------+---------------------------------------------------------------+------------------------------+ - | instantaneous_ops | Ops per Second | Number of commands processed per second | ≥ 0 | Monitored object: | 1 minute | + | 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 | | | | | | | | | @@ -875,7 +875,7 @@ Node Metrics of DCS Redis Instances | | | | | | | | | | | | dcs_cluster_redis_node | | +----------------------------+----------------------------+--------------------------------------------------------------------------------------------------------------------------------+---------------+---------------------------------------------------------------+------------------------------+ - | 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 | Monitored object: | 1 minute | | | | | | | | | | | Unit: byte | | Redis Server of a cluster DCS Redis 3.0, 4.0, or 5.0 instance | | | | | | | | | @@ -885,7 +885,7 @@ Node Metrics of DCS Redis Instances | | | | | | | | | | | | dcs_cluster_redis_node | | +----------------------------+----------------------------+--------------------------------------------------------------------------------------------------------------------------------+---------------+---------------------------------------------------------------+------------------------------+ - | 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 | Monitored object: | 1 minute | | | | | | | | | | | Unit: byte | | Redis Server of a cluster DCS Redis 3.0, 4.0, or 5.0 instance | | | | | | | | | @@ -895,7 +895,7 @@ Node Metrics of DCS Redis Instances | | | | | | | | | | | | dcs_cluster_redis_node | | +----------------------------+----------------------------+--------------------------------------------------------------------------------------------------------------------------------+---------------+---------------------------------------------------------------+------------------------------+ - | 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 | Monitored object: | 1 minute | | | | | | | | | | | Unit: KB/s | | Redis Server of a cluster DCS Redis 3.0, 4.0, or 5.0 instance | | | | | | | | | @@ -905,7 +905,7 @@ Node Metrics of DCS Redis Instances | | | | | | | | | | | | dcs_cluster_redis_node | | +----------------------------+----------------------------+--------------------------------------------------------------------------------------------------------------------------------+---------------+---------------------------------------------------------------+------------------------------+ - | 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 | Monitored object: | 1 minute | | | | | | | | | | | Unit: KB/s | | Redis Server of a cluster DCS Redis 3.0, 4.0, or 5.0 instance | | | | | | | | | @@ -915,7 +915,7 @@ Node Metrics of DCS Redis Instances | | | | | | | | | | | | 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 | + | 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 | | | | | | | | | @@ -925,7 +925,7 @@ Node Metrics of DCS Redis Instances | | | | | | | | | | | | 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 | + | 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 | | | | | | | | | @@ -935,7 +935,7 @@ Node Metrics of DCS Redis Instances | | | | | | | | | | | | 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 | + | 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 | | | | | | | | | @@ -945,7 +945,7 @@ Node Metrics of DCS Redis Instances | | | | | | | | | | | | dcs_cluster_redis_node | | +----------------------------+----------------------------+--------------------------------------------------------------------------------------------------------------------------------+---------------+---------------------------------------------------------------+------------------------------+ - | pubsub_channels | PubSub Channels | Number of Pub/Sub channels | ≥ 0 | Monitored object: | 1 minute | + | 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 | | | | | | | | | @@ -955,7 +955,7 @@ Node Metrics of DCS Redis Instances | | | | | | | | | | | | dcs_cluster_redis_node | | +----------------------------+----------------------------+--------------------------------------------------------------------------------------------------------------------------------+---------------+---------------------------------------------------------------+------------------------------+ - | pubsub_patterns | PubSub Patterns | Number of Pub/Sub patterns | ≥ 0 | Monitored object: | 1 minute | + | 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 | | | | | | | | | @@ -965,7 +965,7 @@ Node Metrics of DCS Redis Instances | | | | | | | | | | | | 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 | + | 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 | | | | | | | | | @@ -975,7 +975,7 @@ Node Metrics of DCS Redis Instances | | | | | | | | | | | | dcs_cluster_redis_node | | +----------------------------+----------------------------+--------------------------------------------------------------------------------------------------------------------------------+---------------+---------------------------------------------------------------+------------------------------+ - | 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 | Monitored object: | 1 minute | | | | | | | | | | | Unit: ms | | Redis Server of a cluster DCS Redis 3.0, 4.0, or 5.0 instance | | | | | | | | | @@ -995,7 +995,7 @@ Node Metrics of DCS Redis Instances | | | | | | | | | | | | dcs_cluster_redis_node | | +----------------------------+----------------------------+--------------------------------------------------------------------------------------------------------------------------------+---------------+---------------------------------------------------------------+------------------------------+ - | keys | Keys | Number of keys in Redis | ≥ 0 | Monitored object: | 1 minute | + | 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 | | | | | | | | | @@ -1005,7 +1005,7 @@ Node Metrics of DCS Redis Instances | | | | | | | | | | | | dcs_cluster_redis_node | | +----------------------------+----------------------------+--------------------------------------------------------------------------------------------------------------------------------+---------------+---------------------------------------------------------------+------------------------------+ - | 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 | Monitored object: | 1 minute | | | | | | | | | | | Unit: count/s | | Redis Server of a cluster DCS Redis 3.0, 4.0, or 5.0 instance | | | | | | | | | @@ -1015,7 +1015,7 @@ Node Metrics of DCS Redis Instances | | | | | | | | | | | | dcs_cluster_redis_node | | +----------------------------+----------------------------+--------------------------------------------------------------------------------------------------------------------------------+---------------+---------------------------------------------------------------+------------------------------+ - | 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 | Monitored object: | 1 minute | | | | | | | | | | | Unit: count/s | | Redis Server of a cluster DCS Redis 4.0 or 5.0 instance | | | | | | | | | @@ -1035,7 +1035,7 @@ Node Metrics of DCS Redis Instances | | | | | | | | | | | | dcs_cluster_redis_node | | +----------------------------+----------------------------+--------------------------------------------------------------------------------------------------------------------------------+---------------+---------------------------------------------------------------+------------------------------+ - | 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 | Monitored object: | 1 minute | | | | | | | | | | | Unit: count/s | | Redis Server of a cluster DCS Redis 4.0 or 5.0 instance | | | | | | | | | @@ -1045,7 +1045,7 @@ Node Metrics of DCS Redis Instances | | | | | | | | | | | | dcs_cluster_redis_node | | +----------------------------+----------------------------+--------------------------------------------------------------------------------------------------------------------------------+---------------+---------------------------------------------------------------+------------------------------+ - | 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 | Monitored object: | 1 minute | | | | | | | | | | | Unit: count/s | | Redis Server of a cluster DCS Redis 4.0 or 5.0 instance | | | | | | | | | @@ -1055,7 +1055,7 @@ Node Metrics of DCS Redis Instances | | | | | | | | | | | | dcs_cluster_redis_node | | +----------------------------+----------------------------+--------------------------------------------------------------------------------------------------------------------------------+---------------+---------------------------------------------------------------+------------------------------+ - | 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 | Monitored object: | 1 minute | | | | | | | | | | | Unit: count/s | | Redis Server of a cluster DCS Redis 4.0 or 5.0 instance | | | | | | | | | @@ -1065,7 +1065,7 @@ Node Metrics of DCS Redis Instances | | | | | | | | | | | | dcs_cluster_redis_node | | +----------------------------+----------------------------+--------------------------------------------------------------------------------------------------------------------------------+---------------+---------------------------------------------------------------+------------------------------+ - | 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 | Monitored object: | 1 minute | | | | | | | | | | | Unit: count/s | | Redis Server of a cluster DCS Redis 4.0 or 5.0 instance | | | | | | | | | @@ -1075,7 +1075,7 @@ Node Metrics of DCS Redis Instances | | | | | | | | | | | | dcs_cluster_redis_node | | +----------------------------+----------------------------+--------------------------------------------------------------------------------------------------------------------------------+---------------+---------------------------------------------------------------+------------------------------+ - | 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 | Monitored object: | 1 minute | | | | | | | | | | | Unit: count/s | | Redis Server of a cluster DCS Redis 4.0 or 5.0 instance | | | | | | | | | @@ -1085,7 +1085,7 @@ Node Metrics of DCS Redis Instances | | | | | | | | | | | | dcs_cluster_redis_node | | +----------------------------+----------------------------+--------------------------------------------------------------------------------------------------------------------------------+---------------+---------------------------------------------------------------+------------------------------+ - | 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 | Monitored object: | 1 minute | | | | | | | | | | | Unit: count/s | | Redis Server of a cluster DCS Redis 4.0 or 5.0 instance | | | | | | | | | @@ -1095,7 +1095,7 @@ Node Metrics of DCS Redis Instances | | | | | | | | | | | | dcs_cluster_redis_node | | +----------------------------+----------------------------+--------------------------------------------------------------------------------------------------------------------------------+---------------+---------------------------------------------------------------+------------------------------+ - | 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 | Monitored object: | 1 minute | | | | | | | | | | | Unit: count/s | | Redis Server of a cluster DCS Redis 4.0 or 5.0 instance | | | | | | | | | @@ -1105,7 +1105,7 @@ Node Metrics of DCS Redis Instances | | | | | | | | | | | | dcs_cluster_redis_node | | +----------------------------+----------------------------+--------------------------------------------------------------------------------------------------------------------------------+---------------+---------------------------------------------------------------+------------------------------+ - | 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 | Monitored object: | 1 minute | | | | | | | | | | | Unit: count/s | | Redis Server of a cluster DCS Redis 4.0 or 5.0 instance | | | | | | | | | @@ -1115,7 +1115,7 @@ Node Metrics of DCS Redis Instances | | | | | | | | | | | | dcs_cluster_redis_node | | +----------------------------+----------------------------+--------------------------------------------------------------------------------------------------------------------------------+---------------+---------------------------------------------------------------+------------------------------+ - | 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 | Monitored object: | 1 minute | | | | | | | | | | | Unit: count/s | | Redis Server of a cluster DCS Redis 4.0 or 5.0 instance | | | | | | | | | @@ -1125,7 +1125,7 @@ Node Metrics of DCS Redis Instances | | | | | | | | | | | | dcs_cluster_redis_node | | +----------------------------+----------------------------+--------------------------------------------------------------------------------------------------------------------------------+---------------+---------------------------------------------------------------+------------------------------+ - | 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 | Monitored object: | 1 minute | | | | | | | | | | | Unit: count/s | | Redis Server of a cluster DCS Redis 4.0 or 5.0 instance | | | | | | | | | @@ -1135,7 +1135,7 @@ Node Metrics of DCS Redis Instances | | | | | | | | | | | | dcs_cluster_redis_node | | +----------------------------+----------------------------+--------------------------------------------------------------------------------------------------------------------------------+---------------+---------------------------------------------------------------+------------------------------+ - | 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 | Monitored object: | 1 minute | | | | | | | | | | | Unit: count/s | | Redis Server of a cluster DCS Redis 4.0 or 5.0 instance | | | | | | | | | @@ -1145,7 +1145,7 @@ Node Metrics of DCS Redis Instances | | | | | | | | | | | | dcs_cluster_redis_node | | +----------------------------+----------------------------+--------------------------------------------------------------------------------------------------------------------------------+---------------+---------------------------------------------------------------+------------------------------+ - | 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 | Monitored object: | 1 minute | | | | | | | | | | | Unit: count | | Redis Server of a cluster DCS Redis 4.0 or 5.0 instance | | | | | | | | | @@ -1155,7 +1155,7 @@ Node Metrics of DCS Redis Instances | | | | | | | | | | | | dcs_cluster_redis_node | | +----------------------------+----------------------------+--------------------------------------------------------------------------------------------------------------------------------+---------------+---------------------------------------------------------------+------------------------------+ - | bandwidth_usage | Bandwidth Usage | Percentage of the used bandwidth to the maximum bandwidth limit | 0–200% | Monitored object: | 1 minute | + | 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 | | | | | | | | | @@ -1173,7 +1173,7 @@ Node Metrics of DCS Redis 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% | Monitored object: | 1 minute | | | | | | | | | | | Unit: % | | Proxy in a Proxy Cluster DCS Redis 3.0 instance | | | | | | | | | @@ -1183,7 +1183,7 @@ Node Metrics of DCS Redis Instances | | | | | | | | | | | | dcs_cluster_proxy_node | | +---------------------+---------------------------------------+-----------------------------------------------------------------------------------------------------+--------------+-------------------------------------------------+------------------------------+ - | 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% | Monitored object: | 1 minute | | | | | | | | | | | Unit: % | | Proxy in a Proxy Cluster DCS Redis 3.0 instance | | | | | | | | | @@ -1193,7 +1193,7 @@ Node Metrics of DCS Redis Instances | | | | | | | | | | | | dcs_cluster_proxy_node | | +---------------------+---------------------------------------+-----------------------------------------------------------------------------------------------------+--------------+-------------------------------------------------+------------------------------+ - | p_connected_clients | Connected Clients | Number of connected clients | ≥ 0 | Monitored object: | 1 minute | + | p_connected_clients | Connected Clients | Number of connected clients | >= 0 | Monitored object: | 1 minute | | | | | | | | | | | | | Proxy in a Proxy Cluster DCS Redis 3.0 instance | | | | | | | | | @@ -1203,7 +1203,7 @@ Node Metrics of DCS Redis Instances | | | | | | | | | | | | dcs_cluster_proxy_node | | +---------------------+---------------------------------------+-----------------------------------------------------------------------------------------------------+--------------+-------------------------------------------------+------------------------------+ - | 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 | Monitored object: | 1 minute | | | | | | | | | | | Unit: packages/second | | Proxy in a Proxy Cluster DCS Redis 3.0 instance | | | | | | | | | @@ -1213,7 +1213,7 @@ Node Metrics of DCS Redis Instances | | | | | | | | | | | | dcs_cluster_proxy_node | | +---------------------+---------------------------------------+-----------------------------------------------------------------------------------------------------+--------------+-------------------------------------------------+------------------------------+ - | 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 | Monitored object: | 1 minute | | | | | | | | | | | Unit: packages/second | | Proxy in a Proxy Cluster DCS Redis 3.0 instance | | | | | | | | | @@ -1223,7 +1223,7 @@ Node Metrics of DCS Redis Instances | | | | | | | | | | | | dcs_cluster_proxy_node | | +---------------------+---------------------------------------+-----------------------------------------------------------------------------------------------------+--------------+-------------------------------------------------+------------------------------+ - | 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 | Monitored object: | 1 minute | | | | | | | | | | | Unit: KB/s | | Proxy in a Proxy Cluster DCS Redis 3.0 instance | | | | | | | | | @@ -1233,7 +1233,7 @@ Node Metrics of DCS Redis Instances | | | | | | | | | | | | dcs_cluster_proxy_node | | +---------------------+---------------------------------------+-----------------------------------------------------------------------------------------------------+--------------+-------------------------------------------------+------------------------------+ - | 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 | Monitored object: | 1 minute | | | | | | | | | | | Unit: KB/s | | Proxy in a Proxy Cluster DCS Redis 3.0 instance | | | | | | | | | @@ -1243,7 +1243,7 @@ Node Metrics of DCS Redis Instances | | | | | | | | | | | | dcs_cluster_proxy_node | | +---------------------+---------------------------------------+-----------------------------------------------------------------------------------------------------+--------------+-------------------------------------------------+------------------------------+ - | 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 | Monitored object: | 1 minute | | | | | | | | | | | Unit: packages/second | | Proxy in a Proxy Cluster DCS Redis 3.0 instance | | | | | | | | | @@ -1253,7 +1253,7 @@ Node Metrics of DCS Redis Instances | | | | | | | | | | | | dcs_cluster_proxy_node | | +---------------------+---------------------------------------+-----------------------------------------------------------------------------------------------------+--------------+-------------------------------------------------+------------------------------+ - | 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 | Monitored object: | 1 minute | | | | | | | | | | | Unit: packages/second | | Proxy in a Proxy Cluster DCS Redis 3.0 instance | | | | | | | | | @@ -1263,7 +1263,7 @@ Node Metrics of DCS Redis Instances | | | | | | | | | | | | dcs_cluster_proxy_node | | +---------------------+---------------------------------------+-----------------------------------------------------------------------------------------------------+--------------+-------------------------------------------------+------------------------------+ - | 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 | Monitored object: | 1 minute | | | | | | | | | | | Unit: KB/s | | Proxy in a Proxy Cluster DCS Redis 3.0 instance | | | | | | | | | @@ -1273,7 +1273,7 @@ Node Metrics of DCS Redis Instances | | | | | | | | | | | | dcs_cluster_proxy_node | | +---------------------+---------------------------------------+-----------------------------------------------------------------------------------------------------+--------------+-------------------------------------------------+------------------------------+ - | 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 | Monitored object: | 1 minute | | | | | | | | | | | Unit: KB/s | | Proxy in a Proxy Cluster DCS Redis 3.0 instance | | | | | | | | | diff --git a/umn/source/operation_guide/backing_up_and_restoring_dcs_instances/configuring_a_backup_policy.rst b/umn/source/operation_guide/backing_up_and_restoring_dcs_instances/configuring_a_backup_policy.rst index ba757b8..57503c4 100644 --- a/umn/source/operation_guide/backing_up_and_restoring_dcs_instances/configuring_a_backup_policy.rst +++ b/umn/source/operation_guide/backing_up_and_restoring_dcs_instances/configuring_a_backup_policy.rst @@ -35,7 +35,7 @@ Procedure +-----------------------------------+--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+ | Retention Period (days) | The number of days that automatically backed up data is retained. | | | | - | | Backup data will be permanently deleted at the end of retention period and cannot be restored. Value range: 1–7. | + | | Backup data will be permanently deleted at the end of retention period and cannot be restored. Value range: 1-7. | +-----------------------------------+--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+ | Start Time | Time at which automatic backup starts. Value: the full hour between 00:00 to 23:00 | | | | 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 9d47380..54394a6 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 @@ -30,7 +30,6 @@ Promoting a Replica to Master .. figure:: /_static/images/en-us_image_0000001322339434.png :alt: **Figure 1** Lists of shards and replicas - **Figure 1** Lists of shards and replicas 7. Click **Promote to Master** in the row containing another replica which is in the "Replica" role. 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 0127c6f..187e717 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 @@ -39,7 +39,7 @@ 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 | + | 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 | +-----------------------------------------------+---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+--------------------------------------------------+--------------------------------------------------+ | 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 | | @@ -57,7 +57,7 @@ Procedure | | | | | | | no: disabled | | | +-----------------------------------------------+---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+--------------------------------------------------+--------------------------------------------------+ - | client-output-buffer-limit-slave-soft-seconds | Number of seconds that the output buffer remains above **client-output-buffer-slave-soft-limit** before the client is disconnected. | 0–60 | 60 | + | client-output-buffer-limit-slave-soft-seconds | Number of seconds that the output buffer remains above **client-output-buffer-slave-soft-limit** before the client is disconnected. | 0-60 | 60 | +-----------------------------------------------+---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+--------------------------------------------------+--------------------------------------------------+ | client-output-buffer-slave-hard-limit | Hard limit (in bytes) on the output buffer of replica clients. Once the output buffer exceeds the hard limit, the client is immediately disconnected. | Depends on the instance type and specifications. | Depends on the instance type and specifications. | +-----------------------------------------------+---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+--------------------------------------------------+--------------------------------------------------+ @@ -81,32 +81,32 @@ Procedure | | | | | | | **allkeys-lfu**: Evict keys by trying to remove the LFU keys first. | | | +-----------------------------------------------+---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+--------------------------------------------------+--------------------------------------------------+ - | lua-time-limit | Maximum time allowed for executing a Lua script (in milliseconds). | 100–5000 | 5,000 | + | lua-time-limit | Maximum time allowed for executing a Lua script (in milliseconds). | 100-5000 | 5,000 | +-----------------------------------------------+---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+--------------------------------------------------+--------------------------------------------------+ | master-read-only | Sets the instance to be read-only. All write operations will fail. | - yes | no | | | | - no | | +-----------------------------------------------+---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+--------------------------------------------------+--------------------------------------------------+ | 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. | +-----------------------------------------------+---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+--------------------------------------------------+--------------------------------------------------+ - | proto-max-bulk-len | Maximum size of a single element request (in bytes). | 1,048,576–536,870,912 | 536,870,912 | + | proto-max-bulk-len | Maximum size of a single element request (in bytes). | 1,048,576-536,870,912 | 536,870,912 | +-----------------------------------------------+---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+--------------------------------------------------+--------------------------------------------------+ - | repl-backlog-size | The replication backlog size (bytes). The backlog is a buffer that accumulates replica data when replicas are disconnected from the master. When a replica reconnects, a partial synchronization is performed to synchronize the data that was missed while replicas were disconnected. | 16,384–1,073,741,824 | 1,048,576 | + | repl-backlog-size | The replication backlog size (bytes). The backlog is a buffer that accumulates replica data when replicas are disconnected from the master. When a replica reconnects, a partial synchronization is performed to synchronize the data that was missed while replicas were disconnected. | 16,384-1,073,741,824 | 1,048,576 | +-----------------------------------------------+---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+--------------------------------------------------+--------------------------------------------------+ - | repl-backlog-ttl | The amount of time, in seconds, before the backlog buffer is released, starting from the last a replica was disconnected. The value **0** indicates that the backlog is never released. | 0–604,800 | 3,600 | + | repl-backlog-ttl | The amount of time, in seconds, before the backlog buffer is released, starting from the last a replica was disconnected. The value **0** indicates that the backlog is never released. | 0-604,800 | 3,600 | +-----------------------------------------------+---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+--------------------------------------------------+--------------------------------------------------+ - | repl-timeout | Replication timeout (in seconds). | 30–3,600 | 60 | + | repl-timeout | Replication timeout (in seconds). | 30-3,600 | 60 | +-----------------------------------------------+---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+--------------------------------------------------+--------------------------------------------------+ - | hash-max-ziplist-entries | Hashes are encoded using a memory efficient data structure when the number of entries in hashes is less than the value of this parameter. | 1–10,000 | 512 | + | hash-max-ziplist-entries | Hashes are encoded using a memory efficient data structure when the number of entries in hashes is less than the value of this parameter. | 1-10,000 | 512 | +-----------------------------------------------+---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+--------------------------------------------------+--------------------------------------------------+ - | hash-max-ziplist-value | Hashes are encoded using a memory efficient data structure when the biggest entry in hashes does not exceed the length threshold indicated by this parameter. | 1–10,000 | 64 | + | hash-max-ziplist-value | Hashes are encoded using a memory efficient data structure when the biggest entry in hashes does not exceed the length threshold indicated by this parameter. | 1-10,000 | 64 | +-----------------------------------------------+---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+--------------------------------------------------+--------------------------------------------------+ - | set-max-intset-entries | When a set is composed of just strings that happen to be integers in radix 10 in the range of 64 bit signed integers, sets are encoded using a memory efficient data structure. | 1–10,000 | 512 | + | set-max-intset-entries | When a set is composed of just strings that happen to be integers in radix 10 in the range of 64 bit signed integers, sets are encoded using a memory efficient data structure. | 1-10,000 | 512 | +-----------------------------------------------+---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+--------------------------------------------------+--------------------------------------------------+ - | zset-max-ziplist-entries | Sorted sets are encoded using a memory efficient data structure when the number of entries in sorted sets is less than the value of this parameter. | 1–10,000 | 128 | + | zset-max-ziplist-entries | Sorted sets are encoded using a memory efficient data structure when the number of entries in sorted sets is less than the value of this parameter. | 1-10,000 | 128 | +-----------------------------------------------+---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+--------------------------------------------------+--------------------------------------------------+ - | zset-max-ziplist-value | Sorted sets are encoded using a memory efficient data structure when the biggest entry in sorted sets does not exceed the length threshold indicated by this parameter. | 1–10,000 | 64 | + | zset-max-ziplist-value | Sorted sets are encoded using a memory efficient data structure when the biggest entry in sorted sets does not exceed the length threshold indicated by this parameter. | 1-10,000 | 64 | +-----------------------------------------------+---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+--------------------------------------------------+--------------------------------------------------+ - | latency-monitor-threshold | Threshold time in latency monitoring. Unit: millisecond. | 0–86,400,000 ms | 0 | + | latency-monitor-threshold | Threshold time in latency monitoring. Unit: millisecond. | 0-86,400,000 ms | 0 | | | | | | | | Set to **0**: Latency monitoring is disabled. | | | | | | | | @@ -140,11 +140,11 @@ Procedure | | | | | | | 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. | | | +-----------------------------------------------+---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+--------------------------------------------------+--------------------------------------------------+ - | slowlog-log-slower-than | Redis records queries that exceed a specified execution time. | 0–1,000,000 | 10,000 | + | slowlog-log-slower-than | Redis records queries that exceed a specified execution time. | 0-1,000,000 | 10,000 | | | | | | | | **slowlog-log-slower-than** is the maximum time allowed, in microseconds, for command execution. If this threshold is exceeded, Redis will record the query. | | | +-----------------------------------------------+---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+--------------------------------------------------+--------------------------------------------------+ - | slowlog-max-len | The maximum allowed number of slow queries that can be logged. Slow query log consumes memory, but you can reclaim this memory by running the **SLOWLOG RESET** command. | 0–1000 | 128 | + | slowlog-max-len | The maximum allowed number of slow queries that can be logged. Slow query log consumes memory, but you can reclaim this memory by running the **SLOWLOG RESET** command. | 0-1000 | 128 | +-----------------------------------------------+---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+--------------------------------------------------+--------------------------------------------------+ .. note:: diff --git a/umn/source/operation_guide/managing_dcs_instances/viewing_redis_slow_logs.rst b/umn/source/operation_guide/managing_dcs_instances/viewing_redis_slow_logs.rst index d6f5d58..9d7037e 100644 --- a/umn/source/operation_guide/managing_dcs_instances/viewing_redis_slow_logs.rst +++ b/umn/source/operation_guide/managing_dcs_instances/viewing_redis_slow_logs.rst @@ -43,7 +43,6 @@ Viewing Slow Logs on the Console .. figure:: /_static/images/en-us_image_0281049655.png :alt: **Figure 1** Slow query log of an instance - **Figure 1** Slow query log of an instance .. |image1| image:: /_static/images/en-us_image_0000001194523041.png diff --git a/umn/source/operation_guide/managing_passwords/changing_instance_passwords.rst b/umn/source/operation_guide/managing_passwords/changing_instance_passwords.rst index e0628fc..4310379 100644 --- a/umn/source/operation_guide/managing_passwords/changing_instance_passwords.rst +++ b/umn/source/operation_guide/managing_passwords/changing_instance_passwords.rst @@ -41,7 +41,7 @@ Procedure - Lowercase letters - Uppercase letters - Digits - - special characters (:literal:`\`~!@#$^&*()-_=+\|{}:,<.>/?`) + - special characters (:literal:`\`~!@#$^&*()-_=+\\|{}:,<.>/?`) #. In the **Change Password** dialog box, click **OK** to confirm the password change. diff --git a/umn/source/operation_guide/managing_passwords/dcs_instance_passwords.rst b/umn/source/operation_guide/managing_passwords/dcs_instance_passwords.rst index 366864d..e57d5a6 100644 --- a/umn/source/operation_guide/managing_passwords/dcs_instance_passwords.rst +++ b/umn/source/operation_guide/managing_passwords/dcs_instance_passwords.rst @@ -21,7 +21,7 @@ Passwords can be configured to control access to your DCS instances, ensuring th - Lowercase letters - Uppercase letters - Digits - - special characters (:literal:`\`~!@#$^&*()-_=+\|{}:,<.>/?`) + - special characters (:literal:`\`~!@#$^&*()-_=+\\|{}:,<.>/?`) Using Passwords Securely ------------------------ diff --git a/umn/source/operation_guide/migrating_data_with_dcs/introduction_to_migration_with_dcs.rst b/umn/source/operation_guide/migrating_data_with_dcs/introduction_to_migration_with_dcs.rst index 3d30fc5..fa41181 100644 --- a/umn/source/operation_guide/migrating_data_with_dcs/introduction_to_migration_with_dcs.rst +++ b/umn/source/operation_guide/migrating_data_with_dcs/introduction_to_migration_with_dcs.rst @@ -35,7 +35,7 @@ The following table describes data migration modes supported by DCS. +------------------------+--------------------------------------------------------------------------------------------------------------------------------+--------------------------------+---------------+---------------+ | | | Single-Node and Master/Standby | Proxy Cluster | Redis Cluster | +------------------------+--------------------------------------------------------------------------------------------------------------------------------+--------------------------------+---------------+---------------+ - | Importing backup files | AOF files in OBS | Y | Y | × | + | Importing backup files | AOF files in OBS | Y | Y | x | | | | | | | | | .. note:: | | | | | | | | | | @@ -59,11 +59,11 @@ The following table describes data migration modes supported by DCS. +------------------------+--------------------------------------------------------------------------------------------------------------------------------+--------------------------------+---------------+---------------+ | | Self-hosted Redis: Redis Cluster | Y | Y | Y | +------------------------+--------------------------------------------------------------------------------------------------------------------------------+--------------------------------+---------------+---------------+ - | | Other Redis: single-node or master/standby | × | × | × | + | | Other Redis: single-node or master/standby | x | x | x | +------------------------+--------------------------------------------------------------------------------------------------------------------------------+--------------------------------+---------------+---------------+ - | | Other Redis: proxy-based cluster | × | × | × | + | | Other Redis: proxy-based cluster | x | x | x | +------------------------+--------------------------------------------------------------------------------------------------------------------------------+--------------------------------+---------------+---------------+ - | | Other Redis: Redis Cluster | × | × | × | + | | Other Redis: Redis Cluster | x | x | x | +------------------------+--------------------------------------------------------------------------------------------------------------------------------+--------------------------------+---------------+---------------+ .. note:: @@ -71,4 +71,4 @@ The following table describes data migration modes supported by DCS. - **DCS for Redis** refers to Redis instances provided by DCS - **Self-hosted Redis** refers to self-hosted Redis on the cloud, from other cloud vendors, or in on-premises data centers. - **Other Redis** refers to Redis services provided by other cloud vendors. - - **Y**: Supported. **×**: Not supported. + - **Y**: Supported. **x**: Not supported. 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 adfce0f..a8cbc94 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 @@ -50,7 +50,7 @@ Scaling - 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. + - 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. Procedure diff --git a/umn/source/permissions_management/creating_a_user_and_granting_dcs_permissions.rst b/umn/source/permissions_management/creating_a_user_and_granting_dcs_permissions.rst index b4415d4..01279ce 100644 --- a/umn/source/permissions_management/creating_a_user_and_granting_dcs_permissions.rst +++ b/umn/source/permissions_management/creating_a_user_and_granting_dcs_permissions.rst @@ -28,7 +28,6 @@ Process Flow .. figure:: /_static/images/en-us_image_0000001196623620.png :alt: **Figure 1** Process of granting DCS permissions - **Figure 1** Process of granting DCS permissions #. .. _dcs-ug-210626004__en-us_topic_0170877287_en-us_topic_0170877287_li10176121316284: diff --git a/umn/source/service_overview/comparing_redis_versions.rst b/umn/source/service_overview/comparing_redis_versions.rst index b3fab09..59ef6d3 100644 --- a/umn/source/service_overview/comparing_redis_versions.rst +++ b/umn/source/service_overview/comparing_redis_versions.rst @@ -18,7 +18,7 @@ When creating a DCS Redis instance, you can select the cache engine version and +========================================+=======================================================+==================================================================================================================================================================================================+ | 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 | + | 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 | +----------------------------------------+-------------------------------------------------------+--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+ 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 4087eef..70f89b2 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 @@ -54,7 +54,6 @@ Architecture .. figure:: /_static/images/en-us_image_0296786164.png :alt: **Figure 1** Master/Standby DCS instance architecture - **Figure 1** Master/Standby DCS instance architecture Architecture description: diff --git a/umn/source/service_overview/dcs_instance_types/proxy_cluster_redis.rst b/umn/source/service_overview/dcs_instance_types/proxy_cluster_redis.rst index 623064c..511171a 100644 --- a/umn/source/service_overview/dcs_instance_types/proxy_cluster_redis.rst +++ b/umn/source/service_overview/dcs_instance_types/proxy_cluster_redis.rst @@ -35,7 +35,6 @@ Each Proxy Cluster instance consists of load balancers, proxies, cluster manager .. figure:: /_static/images/en-us_image_0296786822.png :alt: **Figure 1** Proxy Cluster DCS Redis instance architecture - **Figure 1** Proxy Cluster DCS Redis instance architecture Architecture description: diff --git a/umn/source/service_overview/dcs_instance_types/redis_cluster.rst b/umn/source/service_overview/dcs_instance_types/redis_cluster.rst index ff754bc..43462b8 100644 --- a/umn/source/service_overview/dcs_instance_types/redis_cluster.rst +++ b/umn/source/service_overview/dcs_instance_types/redis_cluster.rst @@ -44,7 +44,6 @@ The Redis Cluster instance type provided by DCS is compatible with the `native R .. figure:: /_static/images/en-us_image_0277578727.png :alt: **Figure 1** Distributed architecture of Redis Cluster - **Figure 1** Distributed architecture of Redis Cluster - Presharding @@ -55,5 +54,4 @@ The Redis Cluster instance type provided by DCS is compatible with the `native R .. figure:: /_static/images/en-us_image_0000001280621500.png :alt: **Figure 2** Redis Cluster presharding - **Figure 2** Redis Cluster presharding 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 c0b3856..cc759d4 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 @@ -42,7 +42,6 @@ Architecture .. figure:: /_static/images/en-us_image_0296784660.png :alt: **Figure 1** Single-node DCS Redis instance architecture - **Figure 1** Single-node DCS Redis instance architecture Architecture description: diff --git a/umn/source/service_overview/ha_and_dr_policies.rst b/umn/source/service_overview/ha_and_dr_policies.rst index 15dbb77..96d1aec 100644 --- a/umn/source/service_overview/ha_and_dr_policies.rst +++ b/umn/source/service_overview/ha_and_dr_policies.rst @@ -11,7 +11,6 @@ Whether you use DCS as the frontend cache or backend data store, DCS is always r .. figure:: /_static/images/en-us_image_0266235346.png :alt: **Figure 1** DCS DR architecture evolution - **Figure 1** DCS DR architecture evolution To meet the reliability requirements of your data and services, you can choose to deploy your DCS instance within a single AZ or across AZs. @@ -27,7 +26,6 @@ Single-AZ deployment means deploying an instance within a physical equipment roo .. figure:: /_static/images/en-us_image_0266235448.png :alt: **Figure 2** HA for a single-node DCS instance deployed within an AZ - **Figure 2** HA for a single-node DCS instance deployed within an AZ **Master/Standby DCS instance**: Data is persisted to disk in the master node and incrementally synchronized and persisted to the standby node, achieving hot standby and data persistence. @@ -36,7 +34,6 @@ Single-AZ deployment means deploying an instance within a physical equipment roo .. figure:: /_static/images/en-us_image_0266235321.png :alt: **Figure 3** HA for a master/standby DCS instance deployed within an AZ - **Figure 3** HA for a master/standby DCS instance deployed within an AZ **Cluster DCS instance**: Similar to a master/standby instance, data in each shard (instance process) of a cluster instance is synchronized between master and standby nodes and persisted on both nodes. @@ -45,7 +42,6 @@ Single-AZ deployment means deploying an instance within a physical equipment roo .. figure:: /_static/images/en-us_image_0266235394.png :alt: **Figure 4** HA for a cluster DCS instance deployed within an AZ - **Figure 4** HA for a cluster DCS instance deployed within an AZ Cross-AZ DR @@ -57,7 +53,6 @@ The master and standby nodes of a master/standby or cluster DCS instance can be .. figure:: /_static/images/en-us_image_0266235441.png :alt: **Figure 5** Cross-AZ deployment of a master/standby DCS instance - **Figure 5** Cross-AZ deployment of a master/standby DCS instance .. note:: diff --git a/umn/source/service_overview/permissions_management.rst b/umn/source/service_overview/permissions_management.rst index 580f1fa..2db433a 100644 --- a/umn/source/service_overview/permissions_management.rst +++ b/umn/source/service_overview/permissions_management.rst @@ -52,41 +52,41 @@ You can grant users permissions by using roles and policies. +---------------------------------------------+----------------+----------------+--------------------+ | Operation | DCS FullAccess | DCS UserAccess | DCS ReadOnlyAccess | +=============================================+================+================+====================+ - | Modifying instance configuration parameters | Y | Y | × | + | Modifying instance configuration parameters | Y | Y | x | +---------------------------------------------+----------------+----------------+--------------------+ - | Deleting background tasks | Y | Y | × | + | Deleting background tasks | Y | Y | x | +---------------------------------------------+----------------+----------------+--------------------+ - | Accessing instances using Web CLI | Y | Y | × | + | Accessing instances using Web CLI | Y | Y | x | +---------------------------------------------+----------------+----------------+--------------------+ - | Modifying instance running status | Y | Y | × | + | Modifying instance running status | Y | Y | x | +---------------------------------------------+----------------+----------------+--------------------+ - | Expanding instance capacity | Y | × | × | + | Expanding instance capacity | Y | x | x | +---------------------------------------------+----------------+----------------+--------------------+ - | Changing instance passwords | Y | Y | × | + | Changing instance passwords | Y | Y | x | +---------------------------------------------+----------------+----------------+--------------------+ - | Modifying DCS instances | Y | × | × | + | Modifying DCS instances | Y | x | x | +---------------------------------------------+----------------+----------------+--------------------+ - | Performing a master/standby switchover | Y | Y | × | + | Performing a master/standby switchover | Y | Y | x | +---------------------------------------------+----------------+----------------+--------------------+ - | Backing up instance data | Y | Y | × | + | Backing up instance data | Y | Y | x | +---------------------------------------------+----------------+----------------+--------------------+ - | Analyzing big keys or hot keys | Y | Y | × | + | Analyzing big keys or hot keys | Y | Y | x | +---------------------------------------------+----------------+----------------+--------------------+ - | Creating DCS instances | Y | × | × | + | Creating DCS instances | Y | x | x | +---------------------------------------------+----------------+----------------+--------------------+ - | Deleting instance backup files | Y | Y | × | + | Deleting instance backup files | Y | Y | x | +---------------------------------------------+----------------+----------------+--------------------+ - | Upgrading instance version | Y | Y | × | + | Upgrading instance version | Y | Y | x | +---------------------------------------------+----------------+----------------+--------------------+ - | Restoring instance data | Y | Y | × | + | Restoring instance data | Y | Y | x | +---------------------------------------------+----------------+----------------+--------------------+ - | Resetting instance passwords | Y | Y | × | + | Resetting instance passwords | Y | Y | x | +---------------------------------------------+----------------+----------------+--------------------+ - | Migrating instance data | Y | Y | × | + | Migrating instance data | Y | Y | x | +---------------------------------------------+----------------+----------------+--------------------+ - | Downloading instance backup data | Y | Y | × | + | Downloading instance backup data | Y | Y | x | +---------------------------------------------+----------------+----------------+--------------------+ - | Deleting DCS instances | Y | × | × | + | Deleting DCS instances | Y | x | x | +---------------------------------------------+----------------+----------------+--------------------+ | Querying instance configuration parameters | Y | Y | Y | +---------------------------------------------+----------------+----------------+--------------------+ diff --git a/umn/source/service_overview/related_services.rst b/umn/source/service_overview/related_services.rst index 645baaf..9f00efd 100644 --- a/umn/source/service_overview/related_services.rst +++ b/umn/source/service_overview/related_services.rst @@ -11,7 +11,6 @@ DCS is used together with other services, including VPC, ECS, IAM, Cloud Eye, CT .. figure:: /_static/images/en-us_image_0277837533.png :alt: **Figure 1** Relationships between DCS and other services - **Figure 1** Relationships between DCS and other services VPC