MongoDB Processes
Cloud Manager will no longer support Automation, Backup, and Monitoring for MongoDB 3.6 and 4.0 after August 30th, 2024. Please upgrade your MongoDB deployment or migrate to Atlas.
- OAuth 2.0 authentication for programmatic access to Cloud Manager is available as a Preview feature.
- The feature and the corresponding documentation might change at any time during the Preview period. To use OAuth 2.0 authentication, create a service account to use in your requests to the Cloud Manager Public API.
- Shut Down MongoDB Processes
- Shut down individual
mongodandmongosprocesses, replica sets and sharded clusters. When you shut down a process, cluster, or replica set, Cloud Manager continues to manage it. - Restart Processes
- Restart a running sharded cluster, replica set, or standalone process directly from the Cloud Manager console. You can also restart individual Cloud Manager-managed MongoDB member processes of a deployment.
- Trigger an Initial Sync for One Process
- Start an initial sync process on one or more MongoDB instances to resynchronize data stored on MongoDB nodes in clusters.
- Suspend or Resume Automation for a Process
- Suspend Cloud Manager Automation to perform for manual maintenance. Automation ignores the process until you re-enable Automation's control.
- Remove a Process from Monitoring
- Removing a process from Cloud Manager monitoring.