Ops Manager is a web application that lets you create, manage, monitor, and back up MongoDB deployments. The web application runs on the Ops Manager server, and software agents run on the servers running MongoDB.
You can use Ops Manager to create new deployments and manage existing ones. To monitor existing deployments, you need to download Ops Manager agents to the servers in the MongoDB deployment.
Prerequisites
Before you begin, confirm the following are in place:
Ops Manager is installed, configured, and running. For installation guidance, see Install Ops Manager with an
rpmPackage, Install Ops Manager with adebPackage, or Install Ops Manager from atar.gzor.zipArchive.An Ops Manager organization and project exist for the deployment.
The MongoDB Automation Agent is installed on each target host. To learn more, see Provision Servers for Automation.
The user account has the
Project Automation Adminrole or theProject Ownerrole.
Networking requirements:
The Automation Agent on each target host must reach Ops Manager on port 8080 (HTTP) or 8443 (HTTPS).
Port 27017 (default) must be open between all MongoDB hosts in the same deployment.
Ops Manager requires outbound HTTPS access to
downloads.mongodb.comandfastdl.mongodb.orgto download MongoDB binaries. For air-gapped environments, configure Local Mode instead.
Get Started with Ops Manager
Ask your Ops Manager administrator for your Ops Manager URL (or an invitation) and whether you have a pre-existing Ops Manager project.
Note
If the Ops Manager is configured to Invitation Only Mode,
you can register only by invitation. The invitation provides a
URL that displays the registration link.
If you do not have a pre-existing project, you will create one upon registering an account.
Verify the Deployment
After the deployment provisions, confirm it is healthy before connecting.
Checkpoint | Verification Step |
|---|---|
Deployment submitted | The Ops Manager UI shows the deployment in your project with a
status of |
Automation Agent goal state reached | In the Ops Manager UI, the Automation Agent status for each host shows a green check, indicating the goal state was reached. |
All members healthy | In the Ops Manager UI, all deployment members show a healthy status with their expected roles. |
Connection succeeds | Connect to the primary using |
Next Steps
After you verify your deployment, you can:
Deploy a replica set: Create a managed replica set. To learn how, see Deploy a Replica Set.
Configure authentication: Set up access control to secure your deployment. To learn how, see Access Control Mechanisms.
Set up backup: Configure continuous backup to protect your data. To learn how, see Backup Process.
Add Automation Agents: Bring more hosts under management. To learn how, see Provision Servers for Automation.