forked from docs/gaussdb-mysql
Changes to gaussdb_mysql_umn from docs/doc-exports#1090 (gaussdbmysql_umn
Modif Reviewed-by: Wagner, Fabian <fabian.wagner@t-systems.com> Co-authored-by: proposalbot <proposalbot@otc-service.com> Co-committed-by: proposalbot <proposalbot@otc-service.com>
This commit is contained in:
parent
fee5a51d20
commit
44fbd5b9e4
Binary file not shown.
Before Width: | Height: | Size: 446 B |
@ -8,6 +8,10 @@ Change History
|
|||||||
+-----------------------------------+--------------------------------------------------------------------------------------------------------------------------------------------+
|
+-----------------------------------+--------------------------------------------------------------------------------------------------------------------------------------------+
|
||||||
| Released On | Description |
|
| Released On | Description |
|
||||||
+===================================+============================================================================================================================================+
|
+===================================+============================================================================================================================================+
|
||||||
|
| 2024-02-28 | Modified the following content: |
|
||||||
|
| | |
|
||||||
|
| | Modified the parameter description in :ref:`Setting Alarm Rules <gaussdb_03_0087>`. |
|
||||||
|
+-----------------------------------+--------------------------------------------------------------------------------------------------------------------------------------------+
|
||||||
| 2023-11-13 | Modified the following content: |
|
| 2023-11-13 | Modified the following content: |
|
||||||
| | |
|
| | |
|
||||||
| | Allowed you to change the node names synchronously during DB instance name change in :ref:`Changing a DB Instance Name <gaussdb_03_0032>`. |
|
| | Allowed you to change the node names synchronously during DB instance name change in :ref:`Changing a DB Instance Name <gaussdb_03_0032>`. |
|
||||||
|
@ -25,17 +25,33 @@ Procedure
|
|||||||
|
|
||||||
#. On the displayed page, set parameters as required.
|
#. On the displayed page, set parameters as required.
|
||||||
|
|
||||||
- Specify **Name** and **Description**.
|
.. table:: **Table 1** Parameter description
|
||||||
- Select **Use template** for **Method**. The template contains the following common metrics: CPU usage, memory usage, and storage space usage.
|
|
||||||
- Click |image2| to enable alarm notification. The validity period is 24 hours by default. If the topics you require are not displayed in the drop-down list, click **Create an SMN topic**. Then, select **Generated alarm** and **Cleared alarm** for **Trigger Condition**.
|
|
||||||
|
|
||||||
.. note::
|
+-----------------------------------+----------------------------------------------------------------------------------------------------------------------------------------------------------+
|
||||||
|
| Parameter | Parameter description |
|
||||||
Cloud Eye sends notifications only within the validity period specified in the alarm rule.
|
+===================================+==========================================================================================================================================================+
|
||||||
|
| Name | Alarm rule name. The system generates a random name, which you can modify. |
|
||||||
|
| | |
|
||||||
|
| | Example value: **alarm-b6al** |
|
||||||
|
+-----------------------------------+----------------------------------------------------------------------------------------------------------------------------------------------------------+
|
||||||
|
| Description | (Optional) Supplementary information about the alarm rule. |
|
||||||
|
+-----------------------------------+----------------------------------------------------------------------------------------------------------------------------------------------------------+
|
||||||
|
| Method | There are two options: **Use existing template**, and **Configure manually**. |
|
||||||
|
+-----------------------------------+----------------------------------------------------------------------------------------------------------------------------------------------------------+
|
||||||
|
| Template | Template to be used. |
|
||||||
|
| | |
|
||||||
|
| | You can select a default alarm template or create a custom template. |
|
||||||
|
+-----------------------------------+----------------------------------------------------------------------------------------------------------------------------------------------------------+
|
||||||
|
| Alarm Notification | Whether to notify users when alarms are triggered. Notifications can be sent by email, text message, or HTTP/HTTPS message. |
|
||||||
|
+-----------------------------------+----------------------------------------------------------------------------------------------------------------------------------------------------------+
|
||||||
|
| Notification Object | Object that receives alarm notifications. You can select the account contact or a topic. |
|
||||||
|
| | |
|
||||||
|
| | - Account contact is the mobile phone number and email address of the registered account. |
|
||||||
|
| | - Topic is used to publish messages and subscribe to notifications. If the required topic is unavailable, create one first and add subscriptions to it. |
|
||||||
|
+-----------------------------------+----------------------------------------------------------------------------------------------------------------------------------------------------------+
|
||||||
|
|
||||||
#. Click **Create**. The alarm rule is created.
|
#. Click **Create**. The alarm rule is created.
|
||||||
|
|
||||||
For operation details, see the *Cloud Eye User Guide*.
|
For operation details, see the *Cloud Eye User Guide*.
|
||||||
|
|
||||||
.. |image1| image:: /_static/images/en-us_image_0000001403218685.png
|
.. |image1| image:: /_static/images/en-us_image_0000001403218685.png
|
||||||
.. |image2| image:: /_static/images/en-us_image_0000001352538844.png
|
|
||||||
|
Loading…
x
Reference in New Issue
Block a user