Huawei Cloud MongoDB
Collect Huawei Cloud MongoDB Metrics
Configuration¶
Install Func¶
It is recommended to activate TrueWatch Integration - Extensions - DataFlux Func (Automata): All prerequisites are automatically installed, please proceed with the script installation.
If you need to deploy Func manually, refer to Manual Deployment of Func
Install Script¶
Note: Please prepare the Huawei Cloud AK in advance (for simplicity, you can grant the global read-only permission
ReadOnlyAccess
)
-
Log in to the Func console, click 【Script Market】, enter the TrueWatch Script Market, and search for
ID: integration_huaweicloud_gaussdb_mongo
-
Click 【Install】, then enter the corresponding parameters: Huawei Cloud AK, SK, and account name
-
Click 【Deploy Startup Script】, the system will automatically create the
Startup
script set and configure the corresponding startup script -
After enabling, you can see the corresponding automatic trigger configuration in 「Management / Automatic Trigger Configuration」. Click 【Execute】 to immediately execute it once without waiting for the scheduled time. Wait a moment, and you can check the execution task records and corresponding logs
Verification¶
- In 「Management / Automatic Trigger Configuration」, confirm whether the corresponding task has the automatic trigger configuration, and check the task records and logs for any exceptions
- In TrueWatch, check if there is asset information in 「Infrastructure - Resource Catalog」
- In TrueWatch, check if there is corresponding monitoring data in 「Metrics」
Metrics¶
Configure Huawei Cloud MongoDB Metrics, you can collect more metrics through configuration Huawei Cloud MongoDB Metrics Details
Metric ID | Metric Name | Metric Meaning | Value Range | Measurement Object | Monitoring Period (Original Metric) |
---|---|---|---|---|---|
nosql001_cpu_usage |
CPU Utilization | This metric is the CPU usage rate collected from the system level. Unit: % | 0~100 % | GeminiDB Mongo instance nodes | 1 minute |
nosql002_mem_usage |
Memory Utilization | This metric is the memory usage rate collected from the system level. Unit: % | 0~100 % | GeminiDB Mongo instance nodes | 1 minute |
nosql003_bytes_out |
Network Output Throughput | Statistics the average traffic output from all network adapters of the measurement object per second. Unit: bytes/s | ≥ 0 bytes/s | GeminiDB Mongo instance nodes | 1 minute |
nosql004_bytes_in |
Network Input Throughput | Statistics the average traffic input from all network adapters of the measurement object per second. Unit: bytes/s | ≥ 0 bytes/s | GeminiDB Mongo instance nodes | 1 minute |
nosql005_disk_usage |
Storage Capacity Utilization | This metric is the storage capacity utilization rate. Unit: % | 0~100 % | GeminiDB Mongo instance nodes | 1 minute |
nosql006_disk_total_size |
Total Storage Capacity | This metric is the total storage capacity of the instance. Unit: GB | ≥ 0 GB | GeminiDB Mongo instance nodes | 1 minute |
nosql007_disk_used_size |
Used Storage Capacity | This metric is the used storage capacity of the instance. Unit: GB | ≥ 0 GB | GeminiDB Mongo instance nodes | 1 minute |
mongodb001_command_ps |
Command Execution Frequency | This metric is used to count the average number of command statements executed per second on the node. Unit: Counts/s | ≥ 0 Counts/s | GeminiDB Mongo instance nodes | 1 minute |
mongodb002_delete_ps |
Delete Statement Execution Frequency | This metric is used to count the average number of delete statements executed per second on the node. Unit: Counts/s | ≥ 0 Counts/s | GeminiDB Mongo instance nodes | 1 minute |
mongodb003_insert_ps |
Insert Statement Execution Frequency | This metric is used to count the average number of insert statements executed per second on the node. Unit: Counts/s | ≥ 0 Counts/s | GeminiDB Mongo instance nodes | 1 minute |
mongodb004_query_ps |
Query Statement Execution Frequency | This metric is used to count the average number of query statements executed per second on the node. Unit: Counts/s | ≥ 0 Counts/s | GeminiDB Mongo instance nodes | 1 minute |
mongodb005_update_ps |
Update Statement Execution Frequency | This metric is used to count the average number of update statements executed per second on the node. Unit: Counts/s | ≥ 0 Counts/s | GeminiDB Mongo instance nodes | 1 minute |
mongodb006_getmore_ps |
Getmore Statement Execution Frequency | This metric is used to count the average number of getmore statements executed per second on the node. Unit: Counts/s | ≥ 0 Counts/s | GeminiDB Mongo instance nodes | 1 minute |
mongodb007_connections_usage |
Current Active Connection Percentage | This metric is used to count the percentage of connections attempting to connect to the instance node relative to the available connections. Unit: % | 0~100 % | GeminiDB Mongo instance nodes | 1 minute |
mongodb008_mem_resident |
Resident Memory | This metric is used to count the current resident memory size. Unit: MB | ≥ 0 MB | GeminiDB Mongo instance nodes | 1 minute |
mongodb009_mem_virtual |
Virtual Memory | This metric is used to count the current virtual memory size. Unit: MB | ≥ 0 MB | GeminiDB Mongo instance nodes | 1 minute |
mongodb010_regular_asserts_ps |
Regular Assert Frequency | This metric is used to count the regular assert frequency. Unit: Counts/s | ≥ 0 Counts/s | GeminiDB Mongo instance nodes | 1 minute |
mongodb011_warning_asserts_ps |
Warning Frequency | This metric is used to count the warning frequency. Unit: Counts/s | ≥ 0 Counts/s | GeminiDB Mongo instance nodes | 1 minute |
mongodb012_msg_asserts_ps |
Message Assert Frequency | This metric is used to count the message assert frequency. Unit: Counts/s | ≥ 0 Counts/s | GeminiDB Mongo instance nodes | 1 minute |
mongodb013_user_asserts_ps |
User Assert Frequency | This metric is used to count the user assert frequency. Unit: Counts/s | ≥ 0 Counts/s | GeminiDB Mongo instance nodes | 1 minute |
mongodb014_queues_total |
Operations Waiting for Locks | This metric is used to count the current number of operations waiting for locks. Unit: Counts | ≥ 0 Counts | GeminiDB Mongo instance nodes | 1 minute |
mongodb015_queues_readers |
Operations Waiting for Read Locks | This metric is used to count the current number of operations waiting for read locks. Unit: Counts | ≥ 0 Counts | GeminiDB Mongo instance nodes | 1 minute |
mongodb016_queues_writers |
Operations Waiting for Write Locks | This metric is used to count the current number of operations waiting for write locks. Unit: Counts | ≥ 0 Counts | GeminiDB Mongo instance nodes | 1 minute |
mongodb017_page_faults |
Page Faults | This metric is used to count the current number of page faults on the node. Unit: Counts | ≥ 0 Counts | GeminiDB Mongo instance nodes | 1 minute |
mongodb018_porfling_num |
Slow Queries | This metric is used to count the current number of slow queries on the node. Unit: Counts | ≥ 0 Counts | GeminiDB Mongo instance nodes | 1 minute |
mongodb019_cursors_open |
Current Maintained Cursors | This metric is used to count the current number of maintained cursors on the node. Unit: Counts | ≥ 0 Counts | GeminiDB Mongo instance nodes | 1 minute |
mongodb020_cursors_timeout |
Service Timeout Cursors | This metric is used to count the current number of service timeout cursors on the node. Unit: Counts | ≥ 0 Counts | GeminiDB Mongo instance nodes | 1 minute |
Object¶
After data synchronization is normal, you can view the data in TrueWatch's 「Infrastructure - Resource Catalog」.
{
"measurement": "huaweicloud_gaussdb_mongo",
"tags": {
"RegionId" : "cn-south-1",
"project_id" : "756ada1aa17e4049b2a16ea41912e52d",
"instance_id" : "16b35ebaba1c44c39d9c24bae742ca97in02",
"enterprise_project_id": "0824ss-xxxx-xxxx-xxxx-12334fedffg",
"instance_name" : "dds-3ed3",
"status" : "normal",
"engine" : "rocksDB"
},
"fields": {
"port" : "8635",
"db_user_name" : "rwuser",
"vpc_id" : "674e9b42-xxxx-xxxx-xxxx-5abcc565b961",
"subnet_id" : "f1df08c5-xxxx-xxxx-xxxx-de435a51007b",
"security_group_id" : "7aa51dbf-xxxx-xxxx-xxxx-dad3c4828b58",
"pay_mode" : "0",
"create_time" : "2024-11-09T15:28:46",
"update_time" : "2024-11-08T13:21:35",
"backup_strategy" : "{Instance JSON Data}",
"datastore" : "{Instance JSON Data}",
"groups" : "[{Instance JSON Data}]",
"time_zone" : "xxxx",
"message" : "{Instance JSON Data}"
}
}
Note: The fields in
tags
andfields
may change with subsequent updatesTip 1: The value of
tags.instance_id
is the instance ID, used as a unique identifierTip 2:
fields.message
fields.backup_strategy
fields.datastore
fields.groups
fields.actions
```