- Create or Import a MongoDB Deployment >
- Add Existing MongoDB Processes to Ops Manager
Add Existing MongoDB Processes to Ops Manager¶
On this page
Overview¶
Ops Manager provides a wizard for adding your existing MongoDB deployments to monitoring and management. The wizard prompts you to install an Automation Agent if none exists, and then prompts you to identify the cluster, replica set, or standalone to add. You can choose to add the deployment to monitoring or to both monitoring and automation.
Considerations¶
Unique Names¶
Deployment items must have unique names within the group.
Important
Replica set, sharded cluster, and shard names within the same group must be unique. Failure to have unique names for the deployment items will result in broken backup snapshots.
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.
Authentication¶
If your deployment requires authentication, you must provide the necessary credentials when adding the deployment to Ops Manager. For information on configuring authentication, see Configure MongoDB Authentication and Authorization.
Automation and Updated Security Settings¶
Adding to automation may affect the security settings of the Ops Manager group or the MongoDB process.
- Enables Ops Manager Group Security Setting.
If the MongoDB process requires authentication but the Ops Manager group does not have authentication settings enabled, upon successful addition of the MongoDB process to automation, the group’s security settings will have the security settings of the newly imported deployment.
Note
The import process only enables the Ops Manager group’s security setting if the group’s security setting is currently not enabled. If the group’s security setting is currently enabled, the import process does not disable the group’s security setting or change its enabled authentication mechanism.
- Updates MongoDB Users.
If the imported MongoDB process already has
mms-backup-agent
andmms-monitoring-agent
users in theadmin
database, and the group’s authentication settings are already enabled or will become enabled by the import process, the roles assigned tomms-backup-agent
andmms-monitoring-agent
will be overriden with the roles designated by the group.
- Updates Ops Manager Group’s MongoDB Users.
Regardless of the group’s security setting, if the MongoDB process to import contains users, the import process will add these users to the group and apply the updated list of users to all processes in the group’s deployment. During the import process, you can remove the users from importing into the group while allowing them to remain in an unmanaged state in the database. Only import the users you want managed since once imported, users cannot be “forgotten”.
- Updates Ops Manager Group’s MongoDB User Roles.
If the MongoDB process contains user-defined roles, the import process will add these roles to the group. You can only remove these roles after the import process completes. That is, you can only remove roles from the group and all its managed processes as a whole.
Note
Custom roles are fully managed by Ops Manager, and the Automation agent will remove custom roles manually added to a database.
- Applies to All Deployments in Group.
The group’s updated security settings apply to all deployments in the group and will restart all deployments in the group with the new setting, including the imported process. All processes will use the Ops Manager automation keyfile upon restart.
If the existing deployment or deployments in the group require a different security profile from the imported process, create a new group to import the MongoDB process.