How to Monitor GeminiDB Mongo in Huawei Cloud
Site24x7 gives your team complete observability into your HuaweiCloud GeminiDB Mongo clusters, catch operation bottlenecks, connection exhaustion, and storage pressure early, delivering real-time visibility into CPU and memory utilization and much more.
Use cases
Queue stability: Prevent write slowdowns by tracking Queued Operations and CPU, enabling timely scaling or load balancing before timeouts occur.
Query efficiency: Reduce latency by monitoring slow query spikes, which helps to identify missing indexes or inefficient queries after deployments.
Connection control: Avoid connection failures by tracking active connections and utilization, enabling proactive tuning before capacity limits are reached.
Setup and configuration
GeminiDB Mongo resources are auto-discovered and monitored during Huawei Cloud integration. To enable monitoring, follow the steps below:
- Navigate to Cloud > Huawei > Add Huawei Monitor. Follow the steps to add a Huawei Cloud monitor.
- While adding or editing a Huawei Cloud monitor, select GeminiDB Mongo from the Service/Resource Types drop-down and click Save.
- Navigate to Cloud > Huawei, select the created Huawei monitor, and then click GeminiDB Mongo to view the performance metrics.
Supported metrics
CPU and memory
Metric name | Description | Units |
| CPU Usage | The percentage of CPU capacity currently consumed by the GeminiDB Mongo instance. | Percentage |
| Memory Usage | The percentage of memory capacity currently consumed by the GeminiDB Mongo instance. | Percentage |
| Resident Memory | The amount of physical memory currently residing in RAM for the MongoDB process. | MB |
| Virtual Memory | The total virtual memory currently allocated to the MongoDB process. | MB |
Storage
Metric name | Description | Units |
| Disk Utilization | The percentage of total disk storage currently consumed by the instance. | Percentage |
| Disk Total Size | The total disk storage capacity provisioned for the instance. | GB |
| Disk Used Size | The total disk storage currently consumed by the instance. | GB |
Network
Metric name | Description | Units |
| Network Output Throughput | The rate of data transmitted out of the instance over the network per second. | Bytes/second |
| Network Input Throughput | The rate of data received by the instance over the network per second. | Bytes/second |
Operations
Metric name | Description | Units |
| COMMAND Per Second | The rate of command operations executed on the instance per second. | Count/second |
| DELETE Per Second | The rate of delete operations executed on the instance per second. | Count/second |
| INSERT Per Second | The rate of insert operations executed on the instance per second. | Count/second |
| QUERY Per Second | The rate of query operations executed on the instance per second. | Count/second |
| UPDATE Per Second | The rate of update operations executed on the instance per second. | Count/second |
| GETMORE Per Second | The rate of getMore cursor operations executed on the instance per second. | Count/second |
Connections
Metric name | Description | Units |
| Active Connections | The number of active client connections currently established to the instance. | Count |
| Connection Utilization | The percentage of available connection capacity currently in use. | Percentage |
Asserts
Metric name | Description | Units |
| Regular Asserts Per Second | The rate of regular assertion errors raised by the instance per second. | Count/second |
| Warning Asserts Per Second | The rate of warning-level assertion errors raised by the instance per second. | Count/second |
| Message Asserts Per Second | The rate of message-level assertion errors raised by the instance per second. | Count/second |
| User Asserts Per Second | The rate of user-generated assertion errors raised by the instance per second. | Count/second |
Queues and cursors
Metric name | Description | Units |
| Total Queued Operations | The total number of operations currently queued waiting to acquire a lock. | Count |
| Queued Read Operations | The number of read operations currently queued waiting to acquire a read lock. | Count |
| Queued Write Operations | The number of write operations currently queued waiting to acquire a write lock. | Count |
| Page Faults | The number of page fault exceptions raised when requested data is not in memory. | Count |
| Slow Query Count | The number of queries currently exceeding the configured slow query threshold. | Count |
| Open Cursors | The number of open cursors currently maintained by the instance. | Count |
| Cursor Timeouts | The number of cursors that have timed out since the last server restart. | Count |
Threshold configuration
You can configure thresholds and alerts for all GeminiDB Mongo metrics to detect performance degradation proactively or connection issues.
Go to Admin > Configuration Profiles > Threshold and Availability to create or modify your alert profiles.
IT Automation
Use Site24x7's IT Automation to resolve common issues with GeminiDB Mongo performance automatically:
- Go to Admin > IT Automation Templates (+)> Add Automation Templates.
- Add tasks such as restarting GeminiDB Mongo-related services or executing custom scripts.
- Trigger GeminiDB Mongo to perform these tasks based on specific alert events.
Configuration rules
You can streamline the monitor setup for multiple GeminiDB Mongo using Configuration Rules. These rules allow you to automatically apply:
- Threshold profiles.
- Notification profiles.
- Tags.
- Monitor group associations.
Run a scan and associate the rule that matches your resource configurations when new GeminiDB Mongo monitors are added.