MongoDB Ops Manager Deployment Guide

MongoDB Ops Manager (MMS) is an infrastructure service for monitoring and backing up MongoDB. The services monitored are free, and the backup service is chargeable. This article takes the latest 4.0.1 as an example of how to install the Configure MongoDB Ops Manager service.

1. Installing and configuring MONGODB Services

[[email protected] ~] # yum -y install mongodb-org.x86_64 mongodb-org-mongos.x86_64 mongodb-org-shell.x86_64 mongodb-org-tools.x86_64 mongodb-org-server.x86_64
The configuration file for creating MongoDB is as follows:

[[email protected] ~] # vi /etc/mongod.conf
systemLog:
  destination: file
  logAppend: true
  path: /var/log/mongodb/mongod.log
storage:
  dbPath: / var / lib / mongo
  journal:
    enabled: true
processManagement:
  fork: true # fork and run in background
  pidFilePath: /var/run/mongodb/mongod.pid # location of pidfile
  timeZoneInfo: / usr / share / zoneinfo
net:
  port: 27017
  bindIp: 0.0.0.0
Start the MongoDB service:

[[email protected] ~] # systemctl start mongod
[[email protected] ~] # systemctl status mongod
● mongod.service-MongoDB Database Server
   Loaded: loaded (/usr/lib/systemd/system/mongod.service; enabled; vendor preset: disabled)
   Active: active (running) since Tue 2018-08-21 11:43:23 CST; 2h 38min ago
     Docs: https://docs.mongodb.org/manual
 Main PID: 29211 (mongod)
   CGroup: /system.slice/mongod.service
           └─29211 / usr / bin / mongod -f /etc/mongod.conf

Aug 21 11:43:21 hdp04 systemd [1]: Starting MongoDB Database Server ...
Aug 21 11:43:22 hdp04 mongod [29208]: 2018-08-21T11: 43: 22.052 + 0800 I CONTROL [main] Automatically disabling TLS 1.0, to force-enable TLS 1.0 specify --sslDisabledProtocols ‘none’
Aug 21 11:43:22 hdp04 mongod [29208]: about to fork child process, waiting until server is ready for connections.
Aug 21 11:43:22 hdp04 mongod [29208]: forked process: 29211
Aug 21 11:43:23 hdp04 mongod [29208]: child process started successfully, parent exiting
Aug 21 11:43:23 hdp04 systemd [1]: Started MongoDB Database Server.
2. Install MongoDB Ops Manager
[[email protected] ~] # yum -y install mongodb-mms.x86_64
[[email protected] ~] # vi /opt/mongodb/mms/conf/conf-mms.properties
#Modify the address of mongodb according to the actual situation
mongo.mongoUri = mongodb: //127.0.0.1: 27017 /? maxPoolSize = 150
mongo.ssl = false
After the installation and configuration is complete, start the service, the default port is 8080:

[[email protected] conf] # /etc/init.d/mongodb-mms start
Generating new Ops Manager private key ...
Starting pre-flight checks
Successfully finished pre-flight checks

Migrate Ops Manager data
   Running migrations ... [OK]
Start Ops Manager server
   Instance 0 starting ...................... [OK]
Starting pre-flight checks
Successfully finished pre-flight checks

Start Backup Daemon ... [OK]

[[email protected] conf] # netstat -antpl | grep 8080
tcp6 0 0 ::: 8080 ::: * LISTEN 10494 / mms-app
3. Configure MongoDB Ops Manager
3.1 Open Ops management interface
Through the service ops port 8080, you can open the web management interface, as shown:

3.2 Register an administrator account

3.3 Setting up Web Server and Email
Set Web Server and Email, other defaults are sufficient, as shown:


3.4 Set user authentication method
The default application database is used here, such as:

3.5 Backup snapshot settings
Use the default settings, such as:


4. Configure MongoDB Ops Manager Agent
Click Agents-> Download & Settings in turn, all agent information will appear:

Choose the type of agent according to the actual needs. Use Automation agent here. The operating system of the environment is Oracle Linux 7, so click the rpm connection corresponding to Centos 7, and the installation operation steps will pop up:

Installation prompts, install and configure each node in turn, taking hdp06 as an example, as follows:

[[email protected] ~] # curl -OL http://192.168.120.99:8080/download/agent/automation/mongodb-mms-automation-agent-manager-5.4.9.5483-1.x86_64.rhel7.rpm
[[email protected] ~] # yum -y localinstall mongodb-mms-automation-agent-manager-5.4.9.5483-1.x86_64.rhel7.rpm
[[email protected] ~] # vi /etc/mongodb-mms/automation-agent.config
mmsBaseUrl = http: //192.168.120.99: 8080
mmsGroupId = 5b7b8bf6dd601873cb8ea94d
mmsApiKey = 5b7b94f0dd601873cb8eb08e7890df416e37a186bcd77e40235210b6
It should be noted that the two options mmsGroupId and mmsApiKey in the configuration file. mmsGroupId uses the value of the agent installation manual that pops up, and mmsApiKey needs to click √Key Generated in the agent installation manual to generate. Start the proxy service after editing the configuration file:

[[email protected] ~] # systemctl start mongodb-mms-automation-agent.service
[[email protected] ~] # systemctl status mongodb-mms-automation-agent.service
After all agents are installed and configured, they will be seen on the web management interface, as shown:

5. Monitor existing Sharding Cluster services
Click the link indicated by the red arrow:

Enter the host name and port number of any node in and click continue, such as:




Follow the prompts in the picture, step by step down to import. The final result is as follows:



MongoDB Ops Manager Deployment Guide