Add Monitored Processes to Automation

Overview

Ops Manager Automation lets you deploy, reconfigure and upgrade your MongoDB databases directly from the Ops Manager console.

If Ops Manager is already monitoring your MongoDB processes, you can add them to Automation.

Automation relies on the MongoDB Agent, which you install on each server that hosts a process to be added to automated management. The MongoDB Agents regularly poll Ops Manager to determine goal configuration and deploy changes as needed.

Considerations

Automation doesn't support all MongoDB options, which can result in failed import attempts. To learn more, see MongoDB Settings and Automation Support.

When adding a MongoDB deployment requiring authentication, you have the option of importing that process's users and roles. During import, Ops Manager prompts you to resolve any conflicts that may occur between the imported users and roles and the managed users and roles.

Prerequisites

• Ensure that your deployment satisfies the deployment requirements.

• Ops Manager must be currently monitoring the MongoDB processes, and the MongoDB Agent must be running. The processes must appear on the Ops Manager Deployment page.

  Tip

  See also:

  Add Existing MongoDB Processes to Ops Manager to enable Ops Manager to automate and monitor your MongoDB processes if Ops Manager does not currently do so.

• If mongod is enabled as a service on the deployment, a race condition might result where systemd starts mongod on reboot, rather than the Automation. To prevent this issue, ensure the mongod service is disabled before you add your deployment to Automation:

  1. Verify whether the mongod service is enabled:

     sudo systemctl is-enabled mongod.service

  2. If the service is enabled, disable it:

     sudo systemctl disable mongod.service

• If the Ops Manager project doesn't have authentication settings enabled but the MongoDB process requires authentication, add the MongoDB Agent user for the Ops Manager project with the appropriate roles. The import process displays the required roles for the user. The added user becomes the project's MongoDB Agent user.

• If the Ops Manager project has authentication settings enabled, add the Ops Manager project's MongoDB Agent user to the MongoDB process.

  • To find the MongoDB Agent user, click Deployments, then Security, then Users.

  • To find the password for the Ops Manager project's MongoDB Agent user, use one of the following methods:

    Using the UI

    Using the API

    Using the Configuration Backup file

    Follow the steps in the Add MongoDB Processes procedure to launch the wizard in the UI. When you reach the modal that says Do you want to add automation to this deployment?:

    1. Select Add Automation and Configure Authentication.

    2. Click Show Password.

    Use the Automation Configuration Resource endpoint:

    curl --user "{PUBLIC-KEY}:{PRIVATE-KEY}" --digest \
      --header "Accept: application/json" \
      --include \
      --request GET "<host>/api/public/v1.0/groups/<Group-ID>/automationConfig"

    Open the mmsConfigBackup file in your preferred text editor and find the autoPwd value.

    Example

    If the Ops Manager project is using Username/Password authentication, add the project's Ops Manager MongoDB Agents User mms-automation to the admin database in the MongoDB deployment to import.

    db.getSiblingDB("admin").createUser(
        {
          user: "mms-automation",
          pwd: <password>,
          roles: [
            'clusterAdmin',
            'dbAdminAnyDatabase',
            'readWriteAnyDatabase',
            'userAdminAnyDatabase',
            'restore',
            'backup'
          ]
        }

• When you add a cluster under Ops Manager, Ops Manager automatically enables log rotation, which could collide with your existing logRotate configuration for mongod or mongos logs. To prevent this collision, do the following:

  • Disable your logRotate configuration for mongod or mongos processes.

  • Remove the systemLog.logRotate and systemLog.logAppend options from the mongod or mongos process configuration to use the default of Ops Manager.

• The import process requires that the authentication credentials and keyfiles are the same on the source and destination clusters. To learn more, see Authentication Credentials on Source and Destination Clusters.

• To successfully import an existing replica set to Ops Manager, the instance must be healthy.

Procedure