Docs

Document Database for MongoDB

Monitoring and alerts

Event monitoring

Document Database for MongoDB supports managing instance event monitoring information through the Cloud Monitoring event center, including viewing event details, creating and editing event rules, etc., helping you promptly discover, locate, and resolve issues. This topic introduces the events that MongoDB supports monitoring and the operation steps related to event management.

Supported monitoring events

MongoDB allows you to monitor exceptional events (Exception) and expected system maintenance events (Maintenance). The following table describes the events of each type.

Sharding cluster instance

Replica set instance

Event type	Event name	Event code	Description
Exception	Sharding cluster instance status abnormal	ShardInstanceStatusAbnormal	When the instance status is abnormal, an event will be triggered.
		Sharding cluster instance backup failure	ShardInstanceBackupFailure	When instance backup (including manual and automatic full backups, incremental backups, and logical backups) fails, an event will be triggered.
		Shard cluster instance primary-secondary failover (due to faults)	ShardInstanceFailover	This event is triggered when an instance encounters a failover (failover).
		The oplog window of sharding cluster instance is insufficient	ShardOplogWindowInsufficient	When the oplog window of an instance is insufficient, an event will be triggered.
Maintenance	Sharding cluster instance primary-secondary failover (task switching)	ShardInstanceSwitchover	When there is a primary-secondary failover (task switching) of an instance, an event will be triggered.

Viewing event monitoring

You can view events related to MongoDB by using the event center in Vitality Cloud Monitor, including the event occurrence time, event source, event name, and event details.

For more information about how to view event monitoring, refer to Viewing cloud service events.

tip

To view monitoring event information on the Cloud service event page, set the product name to Document Database for MongoDB - Replica set or Document Database for MongoDB - Sharding cluster.

On the event list page, you can locate the target time and click Details in the Actions column to view details of the event so that you can locate the reason for event triggering. To further locate the fault, please submit a ticket to contact technical support.

Creating event rules

You can configure alarming rules for events for specified cloud services. When an event that meets the corresponding rule occurs, you will receive alarm notifications at the earliest opportunity, which helps you quickly locate faulty cloud service resources. For specific procedures, refer to Creating event rule.

tip

When configuring Event rule on the Create event rule page, you need to select Resource type as Document Database for MongoDB - Replica set or Document Database for MongoDB - Sharding cluster.

After the event rule is successfully created, you can manage it in the event rule list of Cloud Monitor, including modifying the event rule, or disabling, enabling, or deleting it. For specific procedures, refer to Managing event rules.

Relevant documents

What should be done after receiving an event monitoring alarm for the oplog window being insufficient?

How does Document Database for MongoDB address node failures?

Last updated: 2026.02.12 15:08:56

Event type	Event name	Event code	Description
Exception	Replica set instance status abnormal	ReplicaInstanceStatusAbnormal	When the instance status is abnormal, an event will be triggered.
		Replica set instance backup failure	ReplicaInstanceBackupFailure	When instance backup (including manual and automatic full backups, incremental backups, and logical backups) fails, an event will be triggered.
		Replica set instance primary-secondary failover (due to faults)	ReplicaInstanceFailover	This event is triggered when an instance encounters a failover (failover).
		The oplog window of replica set instance is insufficient	ReplicaOplogWindowInsufficient	When the oplog window of an instance is insufficient, an event will be triggered.
Maintenance	Replica set instance primary-secondary failover (task switching)	ReplicaInstanceSwitchover	This event is triggered when an instance encounters a failover (task switchover).