- Create or Import a MongoDB Deployment >
- Add Monitored Processes to Automation
Add Monitored Processes to Automation¶
On this page
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 using this procedure. If Ops Manager is not monitoring your MongoDB processes, see instead Add Existing MongoDB Processes to Ops Manager, which adds the processes to both Automation and Monitoring.
Automation relies on the Automation Agent, which you install on each server that hosts a process to be added to automated management. The Automation Agents regularly poll Ops Manager to determine goal configuration and deploy changes as needed. An Automation Agent must run as the same user and in the same group as the MongoDB process it will manage.
Considerations¶
Automation Agents can run only on 64-bit architectures.
Automation supports most but not all available MongoDB options. Automation supports the options described in Supported MongoDB Options for Automation.
If the MongoDB process or the Ops Manager group requires authentication, the addition of the MongoDB process to automation can update the security settings. See Automation and Updated Security Settings.
Prerequisites¶
Ops Manager is Monitoring the Processes¶
Ops Manager must be currently monitoring the MongoDB processes, and the Monitoring Agent must be running. The processes must appear in the Ops Manager Deployment tab.
The Automation Agent must have:
- Permission to stop the MongoDB processes. The Automation Agent will restart the processes using the agent’s own set of MongoDB binaries. If you had installed MongoDB with a package manager, use the same package manager to install the Automation Agent. This gives the agent the same owner as MongoDB.
Read
andWrite
permissions on the MongoDB data directories and log directories.
The Process UID and GID must Match the Automation Agent¶
The user (UID) and group (GID) of the MongoDB process must match that of the Automation Agent. For example, if your Automation Agent runs as the “mongod” user in the “mongod” group, the MongoDB process must also run as the “mongod” user in the “mongod” group.
Server Networking Access¶
The servers that host the MongoDB processes must have full networking
access to each other through their fully qualified domain names (FQDNs).
You can view a server’s FQDN by issuing hostname -f
in a shell
connected to the server. Each server must be able to reach every other
server through the FQDN.
Ensure that your network configuration allows each Automation Agent to connect to every MongoDB process listed on the Deployment tab. Ensure that the network and security systems, including all interfaces and firewalls, allow these connections.