Update from the legacy Monitoring Agent

Log in to the Ops Manager Application.

From the notification banner, click Update All Agents.

The Update to MongoDB Agent page opens to start the update process. The Introducing the MongoDB Agent step displays. When you have finished reading this step, click Next.

Add any existing configuration options for your legacy Monitoring Agent.

If Automation did not manage your Monitoring Agent, you can add any Monitoring settings you had before at the Add Custom Configuration Options for your MongoDB Agent (Optional) step.

To add options that you had for your Monitoring Agent, under the Monitoring Configurations section:

1. Type the desired setting in the Setting box and the corresponding value in the Value box.

2. To add more than one Setting, click the + Add Setting link. Another row appears.

3. Repeat until all settings have been added.

4. Once you have added all the settings necessary for your deployment, click Next.

You can click the to remove any settings that you have added.

Install the MongoDB Agent.

1. Click View Agent Install Instructions. The Install Agent Instructions modal opens.

2. From the Select Your Server's Operating System menu, select Amazon Linux - RPM.

3. Click Next. The Install New MongoDB Agent modal opens.

Download the latest version of the MongoDB Agent.

Starting with this step, follow the MongoDB Agent installation modal and copy the commands provided into the Linux shell.

From a system shell on the host that will run the MongoDB Agent, issue the following curl command to download the installer for RHEL 6 for 64-bit x86:

curl -OL https://<OpsManagerHost>:<Port>/download/agent/automation/mongodb-mms-automation-agent-manager-latest.x86_64.rpm

Edit the MongoDB Agent configuration file.

In the directory where you installed the MongoDB Agent, open the automation-agent.config file in your preferred text editor:

sudo vi /etc/mongodb-mms/automation-agent.config

Update the following configuration options:

The resulting changes to the automation-agent.config file should look like the following:

mmsGroupId=<Project ID>
mmsApiKey=<agent API key>
mmsBaseUrl=<application URL>

Optional: Configure the MongoDB Agent to use a proxy server.

To configure the MongoDB Agent to connect to Ops Manager via a proxy server, you must specify the server in the httpProxy environment variable.

In the directory where you installed the MongoDB Agent, open the automation-agent.config file in your preferred text editor.

sudo vi /etc/mongodb-mms/automation-agent.config

Add the following configuration key:

Prepare the data directory.

The data directory stores MongoDB data and must be owned by the mongod user. For an existing MongoDB deployment, ensure the directory has the mongod user as owner. If no MongoDB deployment exists, create the directory and set the owner.

The following commands create a data directory and set the owner as the mongod user:

sudo mkdir /data; sudo chown mongod:mongod /data

Start the MongoDB Agent.

Issue the following command:

sudo service mongodb-mms-automation-agent start

Verify that the MongoDB Agent is running.

In the Install Agent Instructions modal, wait for each deployment to show Verified in the Install the MongoDB Agent step.

Click Next.

Finish the installation of the MongoDB Agent.

In the Install Agent Instructions modal, click Done.

Repeat the installation procedure for each MongoDB host.

Log in to the Ops Manager Application.

From the notification banner, click Update All Agents.

The Update to MongoDB Agent page opens to start the update process. The Introducing the MongoDB Agent step displays. When you have finished reading this step, click Next.

Add any existing configuration options for your legacy Monitoring Agent.

If Automation did not manage your Monitoring Agent, you can add any Monitoring settings you had before at the Add Custom Configuration Options for your MongoDB Agent (Optional) step.

To add options that you had for your Monitoring Agent, under the Monitoring Configurations section:

1. Type the desired setting in the Setting box and the corresponding value in the Value box.

2. To add more than one Setting, click the + Add Setting link. Another row appears.

3. Repeat until all settings have been added.

4. Once you have added all the settings necessary for your deployment, click Next.

You can click the to remove any settings that you have added.

Install the MongoDB Agent.

1. Click View Agent Install Instructions. The Install Agent Instructions modal opens.

2. From the Select Your Server's Operating System menu, select RHEL/CentOS (7.X), SUSE12, Amazon Linux2 - RPM.

3. Click Next. The Install New MongoDB Agent modal opens.

Download the latest version of the MongoDB Agent.

Starting with this step, follow the MongoDB Agent installation modal and copy the commands provided into the Linux shell.

From a system shell on the host that will run the MongoDB Agent, issue the following curl command to download the installer for RHEL 7 for PowerPC:

curl -OL https://<OpsManagerHost>:<Port>/download/agent/automation/mongodb-mms-automation-agent-manager-latest.ppc641e.rhel<version>.rpm

Edit the MongoDB Agent configuration file.

In the directory where you installed the MongoDB Agent, open the automation-agent.config file in your preferred text editor:

sudo vi /etc/mongodb-mms/automation-agent.config

Update the following configuration options:

The resulting changes to the automation-agent.config file should look like the following:

mmsGroupId=<Project ID>
mmsApiKey=<agent API key>
mmsBaseUrl=<application URL>

Optional: Configure the MongoDB Agent to use a proxy server.

To configure the MongoDB Agent to connect to Ops Manager via a proxy server, you must specify the server in the httpProxy environment variable.

In the directory where you installed the MongoDB Agent, open the automation-agent.config file in your preferred text editor.

sudo vi /etc/mongodb-mms/automation-agent.config

Add the following configuration key:

Prepare the data directory.

The data directory stores MongoDB data and must be owned by the mongod user. For an existing MongoDB deployment, ensure the directory has the mongod user as owner. If no MongoDB deployment exists, create the directory and set the owner.

The following commands create a data directory and set the owner as the mongod user:

sudo mkdir /data; sudo chown mongod:mongod /data

Start the MongoDB Agent.

Issue the following command:

sudo service mongodb-mms-automation-agent start

Verify that the MongoDB Agent is running.

In the Install Agent Instructions modal, wait for each deployment to show Verified in the Install the MongoDB Agent step.

Click Next.

Finish the installation of the MongoDB Agent.

In the Install Agent Instructions modal, click Done.

Repeat the installation procedure for each MongoDB host.

Log in to the Ops Manager Application.

From the notification banner, click Update All Agents.

The Update to MongoDB Agent page opens to start the update process. The Introducing the MongoDB Agent step displays. When you have finished reading this step, click Next.

Add any existing configuration options for your legacy Monitoring Agent.

If Automation did not manage your Monitoring Agent, you can add any Monitoring settings you had before at the Add Custom Configuration Options for your MongoDB Agent (Optional) step.

To add options that you had for your Monitoring Agent, under the Monitoring Configurations section:

1. Type the desired setting in the Setting box and the corresponding value in the Value box.

2. To add more than one Setting, click the + Add Setting link. Another row appears.

3. Repeat until all settings have been added.

4. Once you have added all the settings necessary for your deployment, click Next.

You can click the to remove any settings that you have added.

Install the MongoDB Agent.

1. Click View Agent Install Instructions. The Install Agent Instructions modal opens.

2. From the Select Your Server's Operating System menu, select RHEL/CentOS (7.X) Power (ppc64le) - TAR.

3. Click Next. The Install New MongoDB Agent modal opens.

Download the latest version of the MongoDB Agent.

Starting with this step, follow the MongoDB Agent installation modal and copy the commands provided into the Linux shell.

From a system shell on the host that will run the MongoDB Agent, issue the following curl command to download the installer for RHEL 7 for PowerPC:

curl -OL https://<OpsManagerHost>:<Port>/download/agent/automation/mongodb-mms-automation-agent-manager-latest.rhel7_ppc64le.tar.gz

Extract the MongoDB Agent.

You can install the MongoDB Agent in any directory. If you want to move the archive to another directory before extracting, you may do so.

To install the MongoDB Agent, extract the archive:

tar -xvzf mongodb-mms-automation-agent-<VERSION>.rhel7_ppc64le.tar.gz

Change to the extracted binary directory.

Change into the directory that was created after extracting the MongoDB Agent binary:

cd mongodb-mms-automation-agent-<VERSION>.rhel7_ppc64le

Edit the MongoDB Agent configuration file.

In the directory where you installed the MongoDB Agent, open the local.config file in your preferred text editor:

vi <install-path>/local.config

Update the following configuration options:

The resulting changes to the local.config file should look like the following:

mmsGroupId=<Project ID>
mmsApiKey=<agent API key>
mmsBaseUrl=<application URL>

Optional: Configure the MongoDB Agent to use a proxy server.

To configure the MongoDB Agent to connect to Ops Manager via a proxy server, you must specify the server in the httpProxy environment variable.

In the directory where you installed the MongoDB Agent, open the local.config file in your preferred text editor.

vi <install-path>/local.config

Add the following configuration key:

Optional: Create the binary, log, and data directories.

If you have an existing Monitoring Agent user and do not plan on activating Automation, you only need to create the log directory.

Create the following directories to store files that the MongoDB Agent needs.

Run the following commands to create the directories:

sudo mkdir -m 755 -p /var/lib/mongodb-mms-automation
sudo mkdir -m 755 -p /var/log/mongodb-mms-automation
sudo mkdir -m 755 -p /data

By default, the Agent binaries and Ops Manager configuration backup file are located in /var/lib/mongodb-mms-automation. If you want to store these files in a different directory, follow these procedures:

To change the location of the Agent Binaries:

1. Click Deployment, then Agents, and then Downloads & Settings.

2. Below the Download Directory heading, click the pencil icon to the right of the path shown in Download Directory (Linux).

3. Change the path to the new path you want.

4. Click Save.

5. Create the new directory you specified on each host that runs an Agent.

   sudo mkdir -m 755 -p /<newPath>

To change the location of the Agent configuration backup:

1. Open the Agent configuration file in your preferred text editor.

2. Change the mmsConfigBackup setting to the new path for the configuration backup file.

   mmsConfigBackup=/<newPath>/mms-cluster-config-backup.json

3. Save the Agent configuration file.

4. Move the configuration backup file to the new directory.

   sudo mv /var/lib/mongodb-mms-automation/mms-cluster-config-backup.json /<newPath>

Assign permissions to the system user that runs the MongoDB Agent.

Run the following commands:

# Create mongodb user and group if they do not exist
if ! sudo /usr/bin/id -g mongodb &>/dev/null; then
  sudo /usr/sbin/groupadd -r mongodb
fi
# Create mongodb user if they do not exist and assign
# them to the mongodb group
if ! sudo /usr/bin/id mongodb &>/dev/null; then
  sudo /usr/sbin/useradd -M -r -g mongodb \
    -d /var/lib/mongo -s /bin/false \
    -c mongodb mongodb > /dev/null 2>&1
fi
# Grant the mongodb:mongodb user and group permissions
# to manage deployments.
sudo chown mongodb:mongodb /var/lib/mongodb-mms-automation
sudo chown mongodb:mongodb /var/log/mongodb-mms-automation
sudo chown mongodb:mongodb /data

Start the MongoDB Agent.

From the directory in which you installed the MongoDB Agent and as the system user you created in the last step, issue the following command:

nohup ./mongodb-mms-automation-agent \
  --config=local.config \
  >> /var/log/mongodb-mms-automation/automation-agent-fatal.log 2>&1 &

Verify that the MongoDB Agent is running.

In the Install Agent Instructions modal, wait for each deployment to show Verified in the Install the MongoDB Agent step.

Click Next.

Finish the installation of the MongoDB Agent.

In the Install Agent Instructions modal, click Done.

Repeat the installation procedure for each MongoDB host.