For AI agents: a documentation index is available at https://www.mongodb.com/docs/llms.txt — markdown versions of all pages are available by appending .md to any URL path.
Docs Menu

MongoDB Agent for Ops Manager Hosts

The MongoDB Agent is a single binary that connects your MongoDB hosts to Ops Manager. You install the MongoDB Agent on the hosts that run the MongoDB processes you want Ops Manager to manage. Each agent polls Ops Manager to determine the current goal, performs the work needed to reach that goal, and continually reports its status back to Ops Manager.

The MongoDB Agent performs any -- or all -- of the following three functions, depending on what you need:

Function
Description

Automation

Deploys and maintains MongoDB nodes and clusters to match the goal state that your project's automation configuration defines.

Monitoring

Collects statistics from the nodes in your MongoDB deployment and transmits them to Ops Manager so that Ops Manager can report deployment status in real time.

Backup

Takes snapshots of the MongoDB processes you specify so that you can restore your deployment to an earlier state.

To activate the Monitoring or Backup function, use the Ops Manager UI. To activate the Automation function, create a new cluster or import an existing one. To learn how to activate and deactivate each function, see Manage Automation Function.

Agents send deployment configuration information and MongoDB logs only. They don't send any data records from your MongoDB deployment.

Before the introduction of the MongoDB Agent, each function -- Automation, Backup, and Monitoring -- ran as a separate agent binary in your project. These legacy Agents reached end of life in Ops Manager 4.4. To learn about the update process, see My clusters are already managed using all 3 legacy Agents, what will happen?.