Navigation
This version of the documentation is archived and no longer supported. To learn how to upgrade your version of MongoDB Ops Manager, refer to the upgrade documentation.
You were redirected from a different version of the documentation. Click here to go back.

Reactivate Hosts

On this page

Overview

If the Monitoring Agent cannot collect information from a MongoDB process, On-Prem MongoDB Management Service stops monitoring the process. By default, On-Prem MongoDB Management Service stops monitoring a mongos that is unreachable for 24 hours and a mongod that is unreachable for 7 days. Your group might have different default behavior. Ask your system administrator.

When the system stops monitoring a process, the Deployment page marks the process with an x in the Last Ping column. If the instance is a mongod, On-Prem MongoDB Management Service displays a caution icon at the top of each Deployment page.

You can reactivate a deactivated instance whether or not it is running. When you reactivate a host, the Monitoring Agent has an hour to reestablish contact and provide a ping to MMS. If a host is running and reachable, it appears marked with a green circle in the Last Ping column. If it is unavailable, it appears marked with a red square. If it remains unreachable for an hour, MMS deactivates it again.

You can optionally remove a host that you are no longer using. Removed hosts are permanently hidden from MMS. For more information, see Remove Hosts.

Procedure

To reactivate a host:

1

Select the Deployment tab and then the Deployment page.

2

Click the warning icon at the top of the page.

3

Click Reactivate ALL hosts.

4

Add the mongos instances.

←   Manage Hosts Remove Hosts  →