Alarm Management
Resource List
In the resource monitoring list, basic monitoring data is displayed. You can determine the resources you need to view by selecting the resource type in the top left corner of the page, and you can filter the selected resource type using the filter box. By selecting “Cloud Database MongoDB UDB (NVMe)” in the resource types, you can filter the resource list of all nodes for MongoDB (NVMe).
Note: Since MongoDB (NVMe) operates in a clustered mode, whether as a replica set or sharded cluster, it consists of multiple available nodes. Monitoring for each node is conducted separately. Therefore, what is displayed here is the resource information for each individual node, rather than a collective resource name for the entire cluster.
The name of each node can be found in MongoDB “Details”
Some nodes are just virtual nodes (as shown in the red box below), so they will not actually be shown in resource monitoring. Only the parent node in the data shard of the sharded set is a virtual node at present, and the remaining visible nodes are all non-virtual nodes.
For non-virtual nodes, you can copy their names and search them in the resource monitoring list.
Data View
Click the “Data View” button in the resource list to enter the detailed data view page of the selected resource.
Comparison Chart
In the resource monitoring page, besides the “Resource List” tag, there is also a “Comparison Chart” function for multiple resources, which is used to view the monitoring indicator view of multiple resources in a comparative way.
Manage Alarm Templates
Click the “Alarm Templates” option on the right side of the screen to manage current alarm templates. Enter “Cloud Database MongoDB UDB (NVMe)” in the type input field in the upper right corner to search, you can query the currently available alarm templates. The image below shows custom alarm templates and default recommended templates. Default recommended templates cannot be deleted or renamed.
Click “Edit Rule” to view the detailed content of the alarm template. The default recommended template is opened here, so there is no save button, but you can save as a new alarm template based on the current modification.
Go back to the previous page and click “Create Template” to create a new alarm template for a certain resource type.
To create an alarm template corresponding to MongoDB(NVMe), you need to select the corresponding product name in the type, which is “Cloud Database MongoDB UDB (NVMe)“. The creation of the template can be imported from the existing template, at this time the alarm rules of the original template will be copied to the newly created template, or you can choose not to import, a empty template will be created, and you can add new alarm rules yourself.
After clicking create, you will enter the details page of the alarm template, click “Add Rule” in the upper left corner, there will be many optional alarm rules, add the alarm items you need to pay attention to according to actual needs. One template can add serveral alarm rules.
After adding the rules, you need to edit them. For example, the effect after filling in here is that if the disk usage rate is greater than or equal to 80% for three consecutive times in 3 detection cycles, the corresponding alarm information will be sent to the personnel in the corresponding notification group.
Set Alarms
In the resource list, find the resource that needs to add alarms, and click “Alarm Management” in the right operation items.
After clicking the “Alarm Management” button, the “Alarm Management” pop-up window will appear, allowing you to select the appropriate alarm template to bind to the current resource. If the current alarm template list does not contain a suitable one, you can create a new alarm template or edit and modify the existing one.
Note: Editing the existing alarm template will affect all resources that have bound this alarm template.
Click OK to apply this alarm template to the resource. When it is monitored that the resource triggers the corresponding alarm rules in the template, an alarm message will be sent via SMS or email (depending on the alarm method set in the notification group).