FAQ: MongoDB Agent

General

I only use the legacy Monitoring Agent, what does this mean for me?

The MongoDB Agent provides support in this case. The process of switching to using the MongoDB Agent proceeds as follows:

1. When the MongoDB Agent is available, you see the banner notification that your Monitoring Agent is out of date.

2. When you are ready to switch, click Update in the banner. A workflow that guides you through the update process starts.

   1. Read a MongoDB Agent description with a link to documentation.

   2. Specify custom Monitoring configuration options that you use for your Ops Manager project.

   3. Download and install the MongoDB Agent. Ops Manager verifies that the MongoDB Agent is installed correctly on the list of specified servers.

      Note

      Previously configured authentication methods continue to work. You provide the MongoDB authentication information in Monitoring Settings uder the menu.

3. Once you install the MongoDB Agent on a server, the MongoDB Agent enables the Monitoring for projects where Monitoring existed as a standalone Agent before switching to theMongoDB Agent.

4. The MongoDB Agent puts the previously used Monitoring Agents into standby mode and no longer shows them in the UI.

5. The previously used standalone Monitoring Agents can no longer monitor instances. You can stop and remove them when ready.

From this point forward, the MongoDB Agent updates itself after you choose the Confirm and Deploy option for the new version. You no longer need to download the MongoDB Agent each time a new version becomes available!

I only use the legacy Monitoring and Backup Agents, what does this mean for me?

The MongoDB Agent supports this use case. The flow for switching to the MongoDB Agent proceeds as follows:

1. When the MongoDB Agent is available, you see the banner notification that your Monitoring and Backup Agents are out of date.

2. When you are ready to update, click Update in the banner. A workflow that guides you through the update process starts.

   1. Read MongoDB Agent description with a link to documentation.

   2. Specify custom Monitoring and Backup configuration options that you use for your Ops Manager project.

   3. Download and install the MongoDB Agent. Ops Manager verifies that the MongoDB Agent been installed correctly on the list of known servers.

      Note

      Previous authentication methods continue to work. You provide MongoDB authentication information in Monitoring Settings under the menu. To specify Backup user settings, go to Backup under Options > > Edit Credentials.

3. Once the MongoDB Agent is installed on a server, it enables the Monitoring and Backup in projects where the Agents were previously configured.

4. The MongoDB Agent puts the previously used Monitoring and Backup Agents into standby mode and no longer shows them in the UI. The previously used standalone Monitoring Agents can no longer monitor instances. You can stop and remove them when ready.

From this point forward, the MongoDB Agent updates itself if you choose to use the Confirm and Deploy option for a new version. You no longer need to download the MongoDB Agent each time a new version becomes available!

My clusters are already managed using all 3 legacy Agents, what will happen?

The update flow proceeds as follows:

1. When the MongoDB Agent is available, you see the banner notification that your legacy Agents are out of date.

2. When you are ready to update, click Update in the banner. A workflow that guides you through the update process starts.

   1. Read the MongoDB Agent description with link to documentation.

   2. Review a list of your current servers and update them to the MongoDB Agent. As a part of this update process the MongoDB Agent:

      • Stops any legacy Monitoring and Backup Agents.

      • Enables Monitoring and Backup on the servers where Monitoring and Backup were running as Agents.

      • Removes the binaries for the stopped Monitoring and Backup Agents.

      • Unlocks the mms-monitoring-agent or mms-backup-agent users in your MongoDB instances so you can delete them, if desired. The MongoDB Agent uses the mms-automation user to connect to your instances.

From this point forward, the MongoDB Agent works as a single process for Automation, Monitoring, and Backup.