To stop monitoring an ApsaraDB for MongoDB instance, uninstall its monitoring addon from the Managed Service for Prometheus console. Application Real-Time Monitoring Service (ARMS) provides a separate addon for each MongoDB architecture. Identify the correct addon before you begin.
MongoDB addon types
The following table maps each MongoDB architecture to its addon name in the console.
| MongoDB architecture | Addon name |
|---|---|
| Standalone (single node) | Aliyun MongoDB (Single Node Instance) |
| Replica set | Alibaba Cloud Native Observability for Cloud Database MongoDB Replicasets |
| Sharded cluster | Alibaba Cloud MongoDB Cloud Database Shard Cluster Observability (Native) |
| Legacy | Aliyun Cloud Database for MongoDB (Legacy) |
For more information about MongoDB deployment architectures, see Getting started.
Uninstall the addon
The following steps use a standalone instance as an example. For other architectures, select the matching addon from the table above.
Log on to the Managed Service for Prometheus console.
In the left-side navigation pane, click Integration Management.
On the Integrated Environments tab, click the name of the environment instance in the Cloud Service Region section.
On the Component Management tab, click Aliyun MongoDB (Single Node Instance) in the Addon Type section.
NoteIf your instance uses a different architecture, click the corresponding addon listed in the MongoDB addon types table.
Find the target instance, click Uninstall in the Actions column, and then click OK in the confirmation dialog.
