diff --git a/umn/source/_static/images/en-us_image_0000002454002032.png b/umn/source/_static/images/en-us_image_0000002454002032.png new file mode 100644 index 0000000..617abe2 Binary files /dev/null and b/umn/source/_static/images/en-us_image_0000002454002032.png differ diff --git a/umn/source/account_management/creating_an_account.rst b/umn/source/account_management/creating_an_account.rst index 3231db6..e4aa3ef 100644 --- a/umn/source/account_management/creating_an_account.rst +++ b/umn/source/account_management/creating_an_account.rst @@ -20,29 +20,29 @@ Procedure .. table:: **Table 1** Required parameters - +-----------------------------------+--------------------------------------------------------------------------------------------------------------------------------------------------------+ - | Parameter | Description | - +===================================+========================================================================================================================================================+ - | Username | Username of the account. | - | | | - | | The username can consist of 1 to 32 characters and must start with a letter. Only letters, digits, and underscores (_) are allowed. | - +-----------------------------------+--------------------------------------------------------------------------------------------------------------------------------------------------------+ - | Password | Password of the account. The password: | - | | | - | | - Can include 8 to 32 characters. | - | | - Must contain at least three of the following character types: lowercase letters, uppercase letters, digits, and special characters ``~!@#%^*-_=+?`` | - | | - Cannot be a weak password. It cannot be overly simple and easily guessed. | - | | - Cannot be the username or the username spelled backwards. | - +-----------------------------------+--------------------------------------------------------------------------------------------------------------------------------------------------------+ - | Confirm Password | The confirm password must be the same as the entered password. | - +-----------------------------------+--------------------------------------------------------------------------------------------------------------------------------------------------------+ - | Schema | Schema to be associated with the account. You can select an existing schema from the drop-down list. | - | | | - | | The account can be used to access only the associated schemas. | - +-----------------------------------+--------------------------------------------------------------------------------------------------------------------------------------------------------+ - | Permissions | Options: **CREATE**, **DROP**, **ALTER**, **INDEX**, **INSERT**, **DELETE**, **UPDATE**, and **SELECT**. You can select any or a combination of them. | - +-----------------------------------+--------------------------------------------------------------------------------------------------------------------------------------------------------+ - | Description | Description of the account, which cannot exceed 256 characters. | - +-----------------------------------+--------------------------------------------------------------------------------------------------------------------------------------------------------+ + +-----------------------------------+-------------------------------------------------------------------------------------------------------------------------------------------------------+ + | Parameter | Description | + +===================================+=======================================================================================================================================================+ + | Username | Username of the account. | + | | | + | | The username can consist of 1 to 32 characters and must start with a letter. Only letters, digits, and underscores (_) are allowed. | + +-----------------------------------+-------------------------------------------------------------------------------------------------------------------------------------------------------+ + | Password | Password of the account. The password: | + | | | + | | - Can include 8 to 32 characters. | + | | - Must contain at least three of the following character types: lowercase letters, uppercase letters, digits, and special characters ``~!@#%^*-_+?`` | + | | - Cannot be a weak password. It cannot be overly simple and easily guessed. | + | | - Cannot be the username or the username spelled backwards. | + +-----------------------------------+-------------------------------------------------------------------------------------------------------------------------------------------------------+ + | Confirm Password | The confirm password must be the same as the entered password. | + +-----------------------------------+-------------------------------------------------------------------------------------------------------------------------------------------------------+ + | Schema | Schema to be associated with the account. You can select an existing schema from the drop-down list. | + | | | + | | The account can be used to access only the associated schemas. | + +-----------------------------------+-------------------------------------------------------------------------------------------------------------------------------------------------------+ + | Permissions | Options: **CREATE**, **DROP**, **ALTER**, **INDEX**, **INSERT**, **DELETE**, **UPDATE**, and **SELECT**. You can select any or a combination of them. | + +-----------------------------------+-------------------------------------------------------------------------------------------------------------------------------------------------------+ + | Description | Description of the account, which cannot exceed 256 characters. | + +-----------------------------------+-------------------------------------------------------------------------------------------------------------------------------------------------------+ #. Confirm the settings and click **OK**. diff --git a/umn/source/account_management/index.rst b/umn/source/account_management/index.rst index 8c984b8..1ab21ba 100644 --- a/umn/source/account_management/index.rst +++ b/umn/source/account_management/index.rst @@ -9,6 +9,7 @@ Account Management - :ref:`Modifying an Account ` - :ref:`Deleting an Account ` - :ref:`Resetting the Password of an Account ` +- :ref:`Managing Permissions ` .. toctree:: :maxdepth: 1 @@ -18,3 +19,4 @@ Account Management modifying_an_account deleting_an_account resetting_the_password_of_an_account + managing_permissions/index diff --git a/umn/source/account_management/managing_permissions/account_permissions.rst b/umn/source/account_management/managing_permissions/account_permissions.rst new file mode 100644 index 0000000..172709a --- /dev/null +++ b/umn/source/account_management/managing_permissions/account_permissions.rst @@ -0,0 +1,14 @@ +:original_name: ddm_12_0002.html + +.. _ddm_12_0002: + +Account Permissions +=================== + +DDM permissions management is based on MySQL permissions management. DDM supports most of MySQL syntax and permissions. For more information about MySQL accounts and permissions, see `MySQL documentation `__. + +This document describes DDM account rules, permission levels, permission items, and permission operations. + +.. note:: + + DDM Accounts created by CREATE USER or GRANT have nothing to do with accounts in associated RDS instances, and will not be synchronized to RDS instances either. diff --git a/umn/source/account_management/managing_permissions/account_requirements.rst b/umn/source/account_management/managing_permissions/account_requirements.rst new file mode 100644 index 0000000..709c9a9 --- /dev/null +++ b/umn/source/account_management/managing_permissions/account_requirements.rst @@ -0,0 +1,24 @@ +:original_name: ddm_12_0003.html + +.. _ddm_12_0003: + +Account Requirements +==================== + +Account +------- + +Different from MySQL, DDM identifies an account by username, not by username@host. + +Username +-------- + +- Must be case-sensitive. +- Contains 1 to 32 characters and must start with a letter. Only letters, digits, and underscores (_) are allowed. + +Password +-------- + +- Contains 8 to 32 characters. +- Must contain at least three of the following character types: uppercase letters, lowercase letters, digits, and special characters ``~!@#%^*-_+?`` +- Cannot be a weak password that is easily guessed. diff --git a/umn/source/account_management/managing_permissions/index.rst b/umn/source/account_management/managing_permissions/index.rst new file mode 100644 index 0000000..6f2851c --- /dev/null +++ b/umn/source/account_management/managing_permissions/index.rst @@ -0,0 +1,18 @@ +:original_name: ddm_05_0020.html + +.. _ddm_05_0020: + +Managing Permissions +==================== + +- :ref:`Account Permissions ` +- :ref:`Account Requirements ` +- :ref:`Managing Permissions ` + +.. toctree:: + :maxdepth: 1 + :hidden: + + account_permissions + account_requirements + managing_permissions diff --git a/umn/source/account_management/managing_permissions/managing_permissions.rst b/umn/source/account_management/managing_permissions/managing_permissions.rst new file mode 100644 index 0000000..547ca11 --- /dev/null +++ b/umn/source/account_management/managing_permissions/managing_permissions.rst @@ -0,0 +1,220 @@ +:original_name: ddm_12_0004.html + +.. _ddm_12_0004: + +Managing Permissions +==================== + +Permission Levels +----------------- + +- User level (supported) +- Database level (supported) +- Table level (supported) +- Column level (not supported) +- Subprogram level (not supported) +- Global level (not supported) + +Permission Types +---------------- + +DDM supports different permission types by using the GRANT statement. + +=============== ========================================== +Permission Type Description +=============== ========================================== +ALL All permissions +DROP Deleting a table +INDEX Creating/Deleting an index +ALTER Executing ALTER statements +CREATE Creating a table +SELECT Reading table data +INSERT Inserting data to a table +UPDATE Updating data in a table +GRANT Granting permissions to users +REVOKE Deleting a user permission +SET Setting user's passwords +FILE Uploading database permissions from a file +CREATE USER Creating a user +=============== ========================================== + +Precautions +----------- + +- Basic permissions of a DDM account can only be modified on the DDM console. +- If a DDM account has table or database permissions on a schema, the schema will be displayed in the row where the account is located. +- Users created by the CREATE USER statement support only user-level permissions. +- If a DDM account has been associated with a schema, deleting this schema or tables in it does not affect the permissions assigned to the account. +- Permissions cannot be assigned to a DDM account created on the management and control plane unless the account is associated with a schema. + +Permission Operations +--------------------- + +.. important:: + + SHOW GRANTS is supported in versions in 3.0.2 or later. Other functions are available in versions 2.4.1.4 or later. + +**CREATE USER** + +Syntax: + +.. code-block:: + + CREATE USER username IDENTIFIED BY 'password'; + +Example: **Creating an account (whose name is Jenny and whose password is changed from xxxxxx to a custom one)** + +.. code-block:: + + CREATE USER Jenny IDENTIFIED BY 'xxxxxx'; + +.. note:: + + Each username and password must meet the corresponding requirements. + +**DROP USER** + +Syntax: + +.. code-block:: + + DROP USER username + +Example: **Removing user1** + +.. code-block:: + + DROP USER user1; + +**SET PASSWORD** + +Syntax: + +.. code-block:: + + SET PASSWORD FOR 'username'@'%' = 'password' + +.. note:: + + To be compatible with the MySQL syntax, the username must be in the format of 'username'@'%'. + +Example: **Changing the password of Jenny** + +.. code-block:: + + SET PASSWORD FOR 'Jenny'@'%' = 'new_password' + +**GRANT** + +Syntax: + +.. code-block:: + + GRANT + priv_type[, priv_type] ... + ON priv_level + TO user [auth_option] + priv_level: { + | *.* + | db_name.* + | db_name.tbl_name + | tbl_name} + auth_option: { + IDENTIFIED BY 'password' + } + +.. note:: + + If a GRANT statement provides no accounts and does not specify **IDENTIFIED BY**, a message **No account found** will be returned. If **IDENTIFIED BY** is specified, an account will be created accordingly and permissions will be granted to it. + + GRANT ALL [PRIVILEGES] can be used to assign table-, user-, and database-level permissions. + +Example 1: Create a user-level account with all permissions. The username is **user2**. + +Method 1: Create an account and then grant permissions to it. + +.. code-block:: + + CREATE USER user2 IDENTIFIED BY 'password'; + GRANT SELECT, INSERT ON *.* to user2; + +Method 2: Use one SQL statement to create an account and grant it permissions. + +.. code-block:: + + GRANT SELECT, INSERT ON *.* to user2 IDENTIFIED BY 'password'; + +Example 2: Create a database-level account with all permissions. Create account **user3** in database **testdb** and grant the SELECT permissions of database **testdb** to the account. + +Method 1: Create an account and then grant permissions to it. + +.. code-block:: + + CREATE USER user3 IDENTIFIED BY 'password'; + GRANT SELECT ON testdb.* to user3; + +Method 2: Use one SQL statement to create an account and grant it permissions. + +.. code-block:: + + GRANT SELECT ON testdb.* to user3 IDENTIFIED BY 'password'; + +Example 3: Create a table-level account with all permissions. Create account **user4** in database **testdb** and grant all permissions of table **testdb.employees** to the account. + +.. code-block:: + + GRANT ALL PRIVILEGES ON testdb.employees to user4 IDENTIFIED BY 'password'; + +**REVOKE** + +Syntax: + +.. code-block:: + + REVOKE + priv_type [, priv_type] ... + ON priv_level FROM user; + +Example: Deleting CREATE, DROP, and INDEX permissions of user **user4** on table **testdb.emp**. + +.. code-block:: + + REVOKE CREATE,DROP,INDEX ON testdb.emp FROM user4; + +.. note:: + + REVOKE can delete actions at each permission level of an account. The permission level is specified by **priv_level**. + +**SHOW GRANTS** + +Syntax: + +.. code-block:: + + SHOW GRANTS FOR username; + +Example 1: Querying user permissions with any of the following statements: + +.. code-block:: + + SHOW GRANTS; + SHOW GRANTS FOR CURRENT_USER; + SHOW GRANTS FOR CURRENT_USER(); + + +.. figure:: /_static/images/en-us_image_0000002454002032.png + :alt: **Figure 1** Viewing the permissions of the current user + + **Figure 1** Viewing the permissions of the current user + +Example 2: Querying other permissions. This operation can be performed only when the current user can grant user-level permissions. + +.. code-block:: + + mysql> show grants for user4; + +-----------------------------+ + |Grants for user4 | + +-----------------------------+ + |GRANT USAGE ON *.* TO user4 | + +-----------------------------+ + 1 row in set (0.00 sec) diff --git a/umn/source/backups_and_restorations/restoring_metadata.rst b/umn/source/backups_and_restorations/restoring_metadata.rst index 4dcfbc7..ad16d0d 100644 --- a/umn/source/backups_and_restorations/restoring_metadata.rst +++ b/umn/source/backups_and_restorations/restoring_metadata.rst @@ -17,15 +17,17 @@ Prerequisites ------------- - There is a source DDM instance available and associated with an RDS for MySQL instance. This DB instance is the source data node. -- The source data node has been restored to a specified time point. +- The data from the source data node has been restored to the destination data node as it existed at a specified point in time. +- The destination RDS for MySQL instance and the destination DDM instance must be deployed in the same VPC and subnet and have the same security group rules. Constraints ----------- -- The destination DDM instance is not associated with any RDS for MySQL instance and has no schemas or accounts. +- The destination DDM instance is not associated with any RDS for MySQL instance and has no schemas and accounts. - Restoration is not supported if the destination DDM instance is in the primary network and its associated RDS for MySQL instance is in the extended network. - The source DDM instance must be of the version 2.3.2.11 or later, and the destination DDM instance must be of the version 3.0.8 or later. - Time points that data can be restored to depend on the backup policy set on original data nodes. +- The time point to which metadata is restored must be the same as that to which an RDS for MySQL instance is restored. .. _ddm_06_0017__section128315484524: @@ -36,7 +38,7 @@ Restoring Metadata to a Point in Time #. .. _ddm_06_0017__li4793191882712: - :ref:`Create a new DDM instance ` and use it as the destination DDM instance. For details, see\ :ref:`Creating a DDM Instance `. + :ref:`Create a new DDM instance ` and use it as the destination DDM instance. For details, see :ref:`Creating a DDM Instance `. #. In the DDM instance list, locate the source instance and click its name. @@ -48,15 +50,17 @@ Restoring Metadata to a Point in Time .. table:: **Table 1** Parameter description - +--------------------------+-------------------------------------------------------------------------------------------------------------------------------------------------------------+ - | Parameter | Description | - +==========================+=============================================================================================================================================================+ - | Restore To | Specify a point in time. DDM will restore metadata to this point in time using the most recent backup. | - +--------------------------+-------------------------------------------------------------------------------------------------------------------------------------------------------------+ - | Destination DDM Instance | Select the DDM instance created in :ref:`2 `. | - +--------------------------+-------------------------------------------------------------------------------------------------------------------------------------------------------------+ - | Destination Data Nodes | Select the RDS for MySQL instances that have completed PITR. DDM will match the selected data nodes with shard information in the selected metadata backup. | - +--------------------------+-------------------------------------------------------------------------------------------------------------------------------------------------------------+ + +-----------------------------------+--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+ + | Parameter | Description | + +===================================+============================================================================================================================================================================================================================================================================================+ + | Restore To | Specify a point in time. DDM will restore metadata to this point in time using the most recent backup. | + +-----------------------------------+--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+ + | Destination DDM Instance | Select the DDM instance created in :ref:`2 `. | + +-----------------------------------+--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+ + | Destination Data Nodes | Select the RDS for MySQL instances that have completed PITR. DDM will match the selected data nodes with shard information in the selected metadata backup. | + | | | + | | For details about how to perform PITR on RDS for MySQL instances, see `Restoring a DB Instance to a Point in Time `__. | + +-----------------------------------+--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+ #. Click **OK**. If a message is displayed indicating that the metadata is restored successfully, the restoration is complete. @@ -69,7 +73,7 @@ Restoring Metadata Using Backups #. .. _ddm_06_0017__li881143742017: - :ref:`Create a new DDM instance ` and use it as the destination DDM instance. For details, see\ :ref:`Creating a DDM Instance `. + :ref:`Create a new DDM instance ` and use it as the destination DDM instance. For details, see :ref:`Creating a DDM Instance `. #. In the DDM instance list, locate the source instance and click its name. @@ -81,14 +85,16 @@ Restoring Metadata Using Backups .. table:: **Table 2** Parameter description - +--------------------------+-------------------------------------------------------------------------------------------------------------------------------------------------------------+ - | Parameter | Description | - +==========================+=============================================================================================================================================================+ - | Backup Name | Name of the backup to be restored. | - +--------------------------+-------------------------------------------------------------------------------------------------------------------------------------------------------------+ - | Destination DDM Instance | Select the DDM instance created in :ref:`2 `. | - +--------------------------+-------------------------------------------------------------------------------------------------------------------------------------------------------------+ - | Destination Data Nodes | Select the RDS for MySQL instances that have completed PITR. DDM will match the selected data nodes with shard information in the selected metadata backup. | - +--------------------------+-------------------------------------------------------------------------------------------------------------------------------------------------------------+ + +-----------------------------------+--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+ + | Parameter | Description | + +===================================+============================================================================================================================================================================================================================================================================================+ + | Backup Name | Name of the backup to be restored. | + +-----------------------------------+--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+ + | Destination DDM Instance | Select the DDM instance created in :ref:`2 `. | + +-----------------------------------+--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+ + | Destination Data Nodes | Select the RDS for MySQL instances that have completed PITR. DDM will match the selected data nodes with shard information in the selected metadata backup. | + | | | + | | For details about how to perform PITR on RDS for MySQL instances, see `Restoring a DB Instance to a Point in Time `__. | + +-----------------------------------+--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+ #. Click **OK**. If a message is displayed indicating that the metadata is restored successfully, the restoration is complete. diff --git a/umn/source/faqs/rds-related_questions/what_risky_operations_on_rds_for_mysql_will_affect_ddm.rst b/umn/source/faqs/rds-related_questions/what_risky_operations_on_rds_for_mysql_will_affect_ddm.rst index 3a0c1fa..9ada64b 100644 --- a/umn/source/faqs/rds-related_questions/what_risky_operations_on_rds_for_mysql_will_affect_ddm.rst +++ b/umn/source/faqs/rds-related_questions/what_risky_operations_on_rds_for_mysql_will_affect_ddm.rst @@ -44,7 +44,7 @@ What Risky Operations on RDS for MySQL Will Affect DDM? +--------------------------------------------+------------------------------------------------------------------------+--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+ | | Deleting a physical table created on DDM | After a physical table is deleted, data stored on DDM will be lost. The corresponding logical table becomes unavailable on DDM. | +--------------------------------------------+------------------------------------------------------------------------+--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+ - | | Modifying the name of a physical table created on DDM | DDM cannot obtain data of the corresponding logical table, and the logical table becomes unavailable on DDM. | + | | Changing the name of a physical table created on DDM | DDM cannot obtain data of the corresponding logical table, and the logical table becomes unavailable on DDM. | +--------------------------------------------+------------------------------------------------------------------------+--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+ | | Changing a record | Changing a record in a broadcast table will affect the data consistency of shards. | +--------------------------------------------+------------------------------------------------------------------------+--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+ diff --git a/umn/source/getting_started/step_3_create_a_ddm_account.rst b/umn/source/getting_started/step_3_create_a_ddm_account.rst index 307a234..be4db37 100644 --- a/umn/source/getting_started/step_3_create_a_ddm_account.rst +++ b/umn/source/getting_started/step_3_create_a_ddm_account.rst @@ -31,7 +31,7 @@ Procedure +-----------------------------------+-------------------------------------------------------------------------------------------------------------------------------------------------------+ | Schema | Schema to be associated with the DDM account. You can select an existing schema from the drop-down list. | | | | - | | Only the associated schemas can be accessed using the account. | + | | The account can be used to access only the associated schemas. | +-----------------------------------+-------------------------------------------------------------------------------------------------------------------------------------------------------+ | Permissions | Options: **CREATE**, **DROP**, **ALTER**, **INDEX**, **INSERT**, **DELETE**, **UPDATE**, and **SELECT**. You can select any or a combination of them. | +-----------------------------------+-------------------------------------------------------------------------------------------------------------------------------------------------------+ diff --git a/umn/source/monitoring_management/supported_metrics/ddm_instance_metrics.rst b/umn/source/monitoring_management/supported_metrics/ddm_instance_metrics.rst index bf8fbf3..c150826 100644 --- a/umn/source/monitoring_management/supported_metrics/ddm_instance_metrics.rst +++ b/umn/source/monitoring_management/supported_metrics/ddm_instance_metrics.rst @@ -28,37 +28,41 @@ Metrics .. table:: **Table 1** DDM metrics - +------------------------------+----------------------------------+--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+-------------+------------------+--------------------------------+ - | Metric ID | Metric Name | Description | Value Range | Monitored Object | Monitoring Interval (Raw Data) | - +==============================+==================================+================================================================================================================================================================================+=============+==================+================================+ - | ddm_cpu_util | CPU Usage | CPU usage of the DDM instance node | 0—100 | DDM nodes | 1 minute | - +------------------------------+----------------------------------+--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+-------------+------------------+--------------------------------+ - | ddm_mem_util | Memory Usage | Memory usage of the DDM instance node. | 0—100 | DDM nodes | 1 minute | - +------------------------------+----------------------------------+--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+-------------+------------------+--------------------------------+ - | ddm_bytes_in | Network Input Throughput | Incoming traffic per second of the DDM instance node | >= 0 | DDM nodes | 1 minute | - +------------------------------+----------------------------------+--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+-------------+------------------+--------------------------------+ - | ddm_bytes_out | Network Output Throughput | Outgoing traffic per second of the DDM instance node | >= 0 | DDM nodes | 1 minute | - +------------------------------+----------------------------------+--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+-------------+------------------+--------------------------------+ - | ddm_qps | QPS | Requests per second of the DDM instance node | >= 0 | DDM nodes | 1 minute | - +------------------------------+----------------------------------+--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+-------------+------------------+--------------------------------+ - | ddm_read_count | Reads | Read operations of the DDM instance node within each monitoring period | >= 0 | DDM nodes | 1 minute | - +------------------------------+----------------------------------+--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+-------------+------------------+--------------------------------+ - | ddm_write_count | Writes | Write operations of the DDM instance node within a monitoring period | >= 0 | DDM nodes | 1 minute | - +------------------------------+----------------------------------+--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+-------------+------------------+--------------------------------+ - | ddm_slow_log | Slow SQL Logs | Slow SQL logs of DDM-Core | >= 0 | DDM nodes | 1 minute | - +------------------------------+----------------------------------+--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+-------------+------------------+--------------------------------+ - | ddm_rt_avg | Average Response Latency | Average response latency of DDM-Core | >= 0 | DDM nodes | 1 minute | - +------------------------------+----------------------------------+--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+-------------+------------------+--------------------------------+ - | ddm_connections | Connections | Connections of DDM-Core | >= 0 | DDM nodes | 1 minute | - +------------------------------+----------------------------------+--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+-------------+------------------+--------------------------------+ - | ddm_backend_connection_ratio | Percentage of Active Connections | Percentage of active connections (from a DDM node to the target RDS instance) | 0—100 | DDM nodes | 1 minute | - +------------------------------+----------------------------------+--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+-------------+------------------+--------------------------------+ - | ddm_active_connections | Active connections | Active connections of each DDM instance node | >= 0 | DDM nodes | 1 minute | - +------------------------------+----------------------------------+--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+-------------+------------------+--------------------------------+ - | ddm_connection_util | Connection Usage | Percentage of active connections to each DDM instance node | 0—100 | DDM nodes | 1 minute | - +------------------------------+----------------------------------+--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+-------------+------------------+--------------------------------+ - | ddm_node_status_alarm_code | DDM Node Connectivity | Whether each DDM instance node is unavailable. The value can be **0** and **1**. **0** indicates that the node is available, and **1** indicates that the node is unavailable. | 0 or 1 | DDM nodes | 1 minute | - +------------------------------+----------------------------------+--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+-------------+------------------+--------------------------------+ + +----------------------------------------------+---------------------------------------------+--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+-------------+------------------+--------------------------------+ + | Metric ID | Metric Name | Description | Value Range | Monitored Object | Monitoring Interval (Raw Data) | + +==============================================+=============================================+========================================================================================================================================================================================================================================================+=============+==================+================================+ + | ddm_cpu_util | CPU Usage | CPU usage of the DDM instance node | 0—100 | DDM nodes | 1 minute | + +----------------------------------------------+---------------------------------------------+--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+-------------+------------------+--------------------------------+ + | ddm_mem_util | Memory Usage | Memory usage of the DDM instance node. | 0—100 | DDM nodes | 1 minute | + +----------------------------------------------+---------------------------------------------+--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+-------------+------------------+--------------------------------+ + | ddm_bytes_in | Network Input Throughput | Incoming traffic per second of the DDM instance node | >= 0 | DDM nodes | 1 minute | + +----------------------------------------------+---------------------------------------------+--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+-------------+------------------+--------------------------------+ + | ddm_bytes_out | Network Output Throughput | Outgoing traffic per second of the DDM instance node | >= 0 | DDM nodes | 1 minute | + +----------------------------------------------+---------------------------------------------+--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+-------------+------------------+--------------------------------+ + | ddm_qps | QPS | Requests per second of the DDM instance node | >= 0 | DDM nodes | 1 minute | + +----------------------------------------------+---------------------------------------------+--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+-------------+------------------+--------------------------------+ + | ddm_read_count | Reads | Read operations of the DDM instance node within each monitoring period | >= 0 | DDM nodes | 1 minute | + +----------------------------------------------+---------------------------------------------+--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+-------------+------------------+--------------------------------+ + | ddm_write_count | Writes | Write operations of the DDM instance node within a monitoring period | >= 0 | DDM nodes | 1 minute | + +----------------------------------------------+---------------------------------------------+--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+-------------+------------------+--------------------------------+ + | ddm_slow_log | Slow SQL Logs | Slow SQL logs of DDM-Core | >= 0 | DDM nodes | 1 minute | + +----------------------------------------------+---------------------------------------------+--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+-------------+------------------+--------------------------------+ + | ddm_rt_avg | Average Response Latency | Average response latency of DDM-Core | >= 0 | DDM nodes | 1 minute | + +----------------------------------------------+---------------------------------------------+--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+-------------+------------------+--------------------------------+ + | ddm_connections | Connections | Connections of DDM-Core | >= 0 | DDM nodes | 1 minute | + +----------------------------------------------+---------------------------------------------+--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+-------------+------------------+--------------------------------+ + | ddm_backend_connection_ratio | Percentage of Active Connections | Percentage of active connections (from a DDM node to the target RDS instance) | 0—100 | DDM nodes | 1 minute | + +----------------------------------------------+---------------------------------------------+--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+-------------+------------------+--------------------------------+ + | ddm_active_connections | Active connections | Active connections of each DDM instance node | >= 0 | DDM nodes | 1 minute | + +----------------------------------------------+---------------------------------------------+--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+-------------+------------------+--------------------------------+ + | ddm_connection_util | Connection Usage | Percentage of active connections to each DDM instance node | 0—100 | DDM nodes | 1 minute | + +----------------------------------------------+---------------------------------------------+--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+-------------+------------------+--------------------------------+ + | ddm_kernel_fgc_cnt | Kernel Full GC Times | Full GC times of each DDM node per minute | >= 0 counts | DDM nodes | 1 minute | + +----------------------------------------------+---------------------------------------------+--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+-------------+------------------+--------------------------------+ + | ddm_node_status_alarm_code | DDM Node Connectivity | Whether each DDM instance node is unavailable. The value can be **0** and **1**. **0** indicates that the node is available, and **1** indicates that the node is unavailable. | 0 or 1 | DDM nodes | 1 minute | + +----------------------------------------------+---------------------------------------------+--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+-------------+------------------+--------------------------------+ + | ddm_global_sequence_threshold_exceeded_count | Global Secondary Sequences Beyond Threshold | Number of global sequences whose usage exceeds 75%. Usage = Current value/Maximum value. The default threshold is 75%. The maximum value of a global sequence depends on the global sequence type. For example, the maximum value of BIGINT is 2^63-1. | >= 0 counts | DDM instances | 10 minutes | + +----------------------------------------------+---------------------------------------------+--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+-------------+------------------+--------------------------------+ Dimensions ----------