Install the MMS Monitoring Service (6)

The previous sections explain how MMS is going on. It is boring and understandable. However, it is very important to understand how it works first, in the following sections, we will get twice the result with half the effort. Let's take a look at the MMS application installation process. Here I use the RPM package for installation, and the tar package is the same. Overview

The previous sections explain how MMS is going on. It is boring and understandable. However, it is very important to understand how it works first, in the following sections, we will get twice the result with half the effort. Let's take a look at the MMS application installation process. Here I use the RPM package for installation, and the tar package is the same. Overview

The previous sections explain how MMS is going on. It is boring and understandable. However, it is very important to understand how it works first, in the following sections, we will get twice the result with half the effort. Let's take a look at the MMS application installation process. Here I use the RPM package for installation, and the tar package is the same. As mentioned above, MMS is an infrastructure service for monitoring and backing up MongoDB. The installation process is as follows: 1. allocate a server meeting the MMS hardware requirements. 2. install an independent mongodb replica set as the MMS application database. install the SMTP Mail Server 4. install the MMS application package. configure the MMS Service URL, email, and mongo URI connection string 6. start the MMS service. optional installation. For details about the hardware and software requirements for installing the backup service, see the previous section. Install mongodb and install the MMS application database. The official recommendation is to use a replica set. Here I will use a single mongodb.

# vim /etc/yum.repos.d/mongodb.repo [MongoDB]name=MongoDB Repositorybaseurl=http://downloads-distro.mongodb.org/repo/redhat/os/x86_64gpgcheck=0enabled=1# yum install mongodb-org# /etc/init.d/mongod start

Here is a relatively simple installation. For the configuration of relevant parameters, see the previous content. The SMTP service MMS depends on the SMTP service. It uses email as the user. You need to set the user registration and password Based on the email replied by the MMS server. The alarm information is also sent by email. You do not need to configure the SMTP server. Use a third party. Install MMS service package: http://www.mongodb.com/subscription/downloads

# curl -OL https://downloads.mongodb.com/on-prem-mms/rpm/mongodb-mms-1.4.3.106-1.x86_64.rpm# rpm -ivh mongodb-mms-1.4.3.106-1.x86_64.rpm

After MMSRPM is installed, the program is located at/opt/mongodb/mms and runs as a mongodb-mms user. To modify the/opt/mongodb/mms/conf/conf-mms.properties file, make sure that the following parameters are correctly set:

• Mms. centralUrl
• Mms. backupCentralUrl
• Mms. fromEmailAddr
• Mms. replyToEmailAddr
• Mms. adminFromEmailAddr
• Mms. adminEmailAddr
• Mms. bounceEmailAddr
• Mongo. mongoUri
• Mongo. replicaSet

The specific parameter meanings are described in the following section.

mms.centralUrl=http://10.0.101.128:8080mms.backupCentralUrl=http://10.0.101.128:8081mms.fromEmailAddr=monitor@ttlsa.commms.replyToEmailAddr=monitor@ttlsa.commms.adminFromEmailAddr=monitor@ttlsa.commms.adminEmailAddr=monitor@ttlsa.commms.bounceEmailAddr=monitor@ttlsa.commms.userSvcClass=com.xgen.svc.mms.svc.user.UserSvcDbmms.emailDaoClass=com.xgen.svc.core.dao.email.JavaEmailDaomms.mail.transport=smtpmms.mail.hostname=smtp.exmail.qq.commms.mail.port=25mms.mail.username=monitor@ttlsa.commms.mail.password=************mms.mail.tls=mongo.mongoUri=mongodb://127.0.0.1:27017/mongo.replicaSet=mongo.backupdb.mongoUri=mongo.backupdb.replicaSet=ping.queue.size=100ping.thread.count=100increment.queue.size=14000increment.thread.count=35increment.gle.freq=70increment.offer.time=120000aws.accesskey=aws.secretkey=reCaptcha.enabled=falsereCaptcha.public.key=reCaptcha.private.key=twilio.account.sid=twilio.auth.token=twilio.from.num=graphite.hostname=graphite.port=2003snmp.default.hosts=snmp.listen.port=11611snmp.default.heartbeat.interval=300

Start the service to start the mongodb-mms Service:

# /etc/init.d/mongodb-mms startMigrate MMS data   Running migrations...[  OK  ]Start MMS server   Instance 0 starting.......[  OK  ]Start Backup HTTP Server   Instance 0 starting.....[  OK  ]Start Backup Alert Process[  OK  ]

If the startup fails, view the log. Port used:

# netstat -ntplu | grep mmstcp        0      0 0.0.0.0:8080                0.0.0.0:*                   LISTEN      11993/mms-app       tcp        0      0 0.0.0.0:8081                0.0.0.0:*                   LISTEN      12754/mms-app       tcp        0      0 0.0.0.0:8091                0.0.0.0:*                   LISTEN      12754/mms-app       tcp        0      0 :::8092                     :::*                        LISTEN      13206/mms-app       tcp        0      0 ::ffff:127.0.0.1:8650       :::*                        LISTEN      13206/mms-app       udp        0      0 0.0.0.0:11611               0.0.0.0:*                               11993/mms-app

Created database:

# mongoMongoDB shell version: 2.6.3connecting to: test> show dbsadmin                   (empty)alerts                  0.203GBapiv3                   0.578GBbackupagent             0.078GBbackupalerts            0.078GBbackupbilling           0.078GBbackupconfig            (empty)backupjobs              0.078GBbackuplogs              2.077GBbackupsnapshot          0.078GBcloudconf               0.203GBlocal                   0.078GBmmsdb                   0.078GBmmsdbagentlog           1.078GBmmsdbautomation         0.078GBmmsdbautomationlog      0.078GBmmsdbconfig             0.328GBmmsdbdays               0.078GBmmsdbhours              0.078GBmmsdbjobs               0.078GBmmsdbminutes-even       0.078GBmmsdbminutes-odd        0.078GBmmsdbpings              0.578GBmmsdbprovisioning       0.078GBmmsdbqueues             0.078GBmmsdbrrdsampling        0.078GBmongo-distributed-lock  0.078GB

So far, the mms monitoring function has been installed. Access http: // 10.0.101.128: 8080 for management. Log on directly if you have an account. If not, you need to register. The user role is the Owner. To log on again after logging out, you must use the preceding email and password to log on. At this point, the MMS monitoring server has been set. Next, you need to set up the MMS monitoring proxy. The installation of the backup service MMS backup service is only available for trial use. The official version requires payment. The backup service will be available later.

Original article address: MMS monitoring service installation (6). Thank you for sharing it with me.