Stop Managing and/or Monitoring One Deployment
On this page
- 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.
Cloud Manager uses Automation to manage your deployments but can monitor and back up your deployments without Automation.
If you no longer want to use Cloud Manager for one or both of these capabilities, you can stop Cloud Manager from either:
Managing your deployment while still monitoring it and backing it up, or
Managing, monitoring, and backing up your deployment
After you stop Cloud Manager from managing a deployment, you cannot use Cloud Manager
to upgrade, stop, start, or change that deployment's configuration in
any way. If you want to
shut down your deployment
before stop Cloud Manager from managing it, do that first. Otherwise, you
must connect to each process using mongosh to
shut down the process directly.
If you stop using Cloud Manager to monitor your deployment, any associated snapshots are deleted and all historic monitoring data is removed.
Stopping Cloud Manager from managing or monitoring your deployment does not
affect the deployment's mongod and mongos processes. These
processes continue to run uninterrupted unless you explicitly shut it
down first.
Considerations
Disable All Deployments
To unmanage all deployments at once, see Remove Project from Automation.
Prerequisites
This tutorial explains how to stop Cloud Manager Automation from managing your deployment. You may need to complete some additional tasks before you remove your deployment from Cloud Manager Automation. The following table highlights which actions you need to take before starting this tutorial.
If you want to... | You first need to... |
|---|---|
Stop monitoring a deployment | |
Terminate a deployment | |
Stop Cloud Manager from managing a Sharded Cluster |
Procedure
Note
As an alternative to disabling automation for a deployment, you can temporarily suspend automation for that deployment.
This is useful if you need to temporarily shut down the deployment for maintenance, and do not want Cloud Manager to automatically start the deployment back up until you are ready.
In MongoDB Cloud Manager, go to the Deployment page for your project.
If it is not already displayed, select the organization that contains your desired project from the Organizations menu in the navigation bar.
If it's not already displayed, select your desired project from the Projects menu in the navigation bar.
If the Deployment page is not already displayed, click Deployment in the sidebar.
The Deployment page displays.
Go to the Processes page.
Click the Processes tab for your deployment.
The Processes page displays.
Choose to stop Cloud Manager from managing and/or monitoring the deployment.
When you stop Cloud Manager from managing your deployment, you must select one of the following options:
Unmanage this item in Cloud Manager but continue
to monitor | Removes the process from management only. You can no longer
control the process through Cloud Manager, but Cloud Manager continues to
display its status and track its metrics. |
Completely remove from Cloud Manager | Removes the processes from both management and monitoring.
Cloud Manager no longer displays the process. All backups are
terminated and all backup snapshots are deleted. |