- Create or Import a MongoDB Deployment >
- Add Existing MongoDB Processes to Monitoring
Add Existing MongoDB Processes to Monitoring¶
On this page
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 processes.
If you add processes from an environment that uses authentication, you must add each mongod process 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 have a running Monitoring Agent on one of the servers that hosts the MongoDB processes.
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.
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.
Select the Deployment tab and then the Deployment page.¶
Click Add and select Import Existing for Monitoring.¶
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 Configure Monitoring Agent 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. |