- Import an Existing MongoDB Deployment >
- Reactivate Monitoring for a Process
Reactivate Monitoring for a Process¶
Overview¶
If the Monitoring Agent cannot collect information from a MongoDB process, Ops Manager stops monitoring the process. By default, Ops Manager 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, Ops Manager displays a caution icon at the top of each
Deployment page.
You can reactivate monitoring for the process whether or not the process is running. When you reactivate monitoring, the Monitoring Agent has an hour to reestablish contact and provide a ping to Ops Manager. If a process 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, Ops Manager again stops monitoring the process.
You can optionally remove a process that you are no longer using. Removed processes are permanently hidden from Ops Manager. For more information, see Remove Hosts.
Procedure¶
To reactivate monitoring for a process:
Select the Deployment tab and then the Deployment page.¶
Click the warning icon at the top of the page.¶
Click Reactivate ALL hosts.¶
The processes that are now running and reachable by the Monitoring Agent will appear marked with green circles in the Last Ping column.
The processes that are unavailable or unreachable will appear marked with a red square. If a process does not send a ping within an hour after reactivation, it is deactivated again.
Add the mongos instances.¶
To activate the mongos instances, click the Add
Host button and enter the hostname, port, and optionally an admin
database username and password. Then click Add.