Navigation

Stop Managing and/or Monitoring One Deployment

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 the mongo shell 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

Script Deployment after Disabling Automation

If you are disabling automation for a deployment and want to stop and start the deployment from another host afterward, you can create scripts for stopping and starting the deployment.

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 Stop backing up the deployment
Terminate a deployment Shut down the deployment
Stop Cloud Manager from managing a Sharded Cluster

Shut down any mongos processes associated with a sharded cluster.

The Remove from Cloud Manager option is unavailable for running mongos processes.

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.

1

Click Deployment, then the Processes tab, then the Topology view.

2

Click the ellipsis icon next to the desired deployment.

3

Select Remove from Cloud Manager.

4

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.
5

Confirm that you want automation and/or monitoring disabled for the deployment.

  1. Click Remove <Deployment>.

    <Deployment> stands in for the deployment being removed: Sharded Cluster, Replica Set or Standalone

  2. If prompted for a verification code, enter the code and then click Remove <Deployment> again.

6

Click Review & Deploy to review your changes.

Cloud Manager displays your proposed changes.

  1. If you are satisfied, click Confirm & Deploy.
  2. If you want to make further configuration changes, click Cancel. Click Modify for the cluster to make additional changes.