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.

Add Existing MongoDB Processes to Monitoring

Overview

You can monitor existing MongoDB processes in Ops Manager by adding the hostnames and ports of the processes. Ops Manager will start monitoring the mongod and mongos instances.

If you add processes from an environment that uses authentication, you must add each mongod instance separately and explicitly set the authentication credentials on each.

If you add processes in an environment that does not use authentication, you can manually add one process from a replica set or a sharded cluster as a seed. Once the Monitoring Agent has the seed, it automatically discovers all the other nodes in the replica set or sharded cluster.

Unique Replica Set Names

Do not add two different replica sets with the same name. Ops Manager uses the replica set name to identify which set a member belongs to.

Preferred Hostnames

If the MongoDB process is accessible only by specific hostname or IP address, or if you need to specify the hostname to use for servers with multiple aliases, set up a preferred hostname. For details, see the Preferred Hostnames setting in Group Settings.

Prerequisite

You must install a Monitoring Agent to your infrastructure.

To monitor or back up MongoDB 3.0 deployments, you must install Ops Manager 1.6 or higher. To monitor a MongoDB 3.0 deployment, you must also run Monitoring Agent version 2.7.0 or higher.

Important

If you provision your own servers and if you use MongoDB Enterprise, you must install the prerequisite packages on the servers before deploying MongoDB Enterprise on the servers.

Add MongoDB Processes

If your deployments use authentication, perform this procedure for each process. If your deployment does not use authentication, add one process from a replica set or sharded cluster and Ops Manager will discover the other nodes in the replica set or sharded cluster.

1

Select the Deployment tab and then the Deployment page.

2

Select view mode and then select Add Host.

3

Enter information for the MongoDB process.

Enter the following information, as appropriate:

Host Type The type of MongoDB deployment.
Internal Hostname The hostname of the MongoDB instance as seen from the Monitoring Agent.
Port The port on which the MongoDB instance runs.
Auth Mechanism

The authentication mechanism used by the host.

See Add Monitoring Agent User for MONGODB-CR, Configure Monitoring Agent for LDAP, or Configure the Monitoring Agent for Kerberos for setting up user credentials.

DB Username If the authentication mechanism is MONGODB-CR or LDAP, the username used to authenticate the Monitoring Agent to the MongoDB deployment.
DB Password If the authentication mechanism is MONGODB-CR or LDAP, the password used to authenticate the Monitoring Agent to the MongoDB deployment.
My deployment supports SSL for MongoDB connections If checked, the Monitoring Agent must have a trusted CA certificate in order to connect to the MongoDB instances. See Configure Monitoring Agent for SSL.
4

Click Add.

To view agent output logs, click the Administration tab, then Agents, and then view logs for the agent.

To view process logs, click the Deployment tab, then the Deployment page, then the process, and then the Logs tab.

For more information on logs, see View Logs.