Navigation

mongocli ops-manager monitoring stop

The monitoring stop command stops the MongoDB Agent from monitoring the host that you specify. You can also stop Monitoring for one host in Ops Manager using the UI and API.

You must have Project Monitoring Admin or Project Owner role to stop the MongoDB Agent from monitoring a host.

mongocli ops-manager|om monitoring stop <hostId>
[ --force ]
[ --profile|-P <profile-name> ]
[ --projectId <project-ID> ]
Option
Type
Description
Required?
<hostId>
string

Unique identifier of the host you want to stop monitoring.

Use the mongocli ops-manager process list command to retrieve unique identifiers for your hosts.

yes
Option
Type
Description
Required?
--force
Bypasses the confirmation prompt.
no
--profile, -P
string
Name of the profile where the public and private keys for the project are saved. If omitted, uses the default profile. To learn more about creating a profile, see Configure the MongoDB CLI.
no
--projectId
string

Unique identifier of the project. If omitted, uses the project ID in the profile or environment variable.

no

The command prints the following field to the terminal if the command succeeds. If the command prints an error, see Troubleshooting for recommended solutions.

Stopped monitoring '<hostId>'

The following command uses the mongocli ops-manager monitoring stop command to stop the MongoDB Agent from monitoring one host. It uses the default profile to access Ops Manager.

mongocli ops-manager monitoring stop 5c8100bcf2a30b12ff88258f
Are you sure you want to delete: 5c8100bcf2a30b12ff88258f Yes

The previous command prints the following to the terminal.

Stopped monitoring '5c8100bcf2a30b12ff88258f'
Give Feedback

On this page

  • Syntax
  • Arguments
  • Options
  • Output
  • Example