Docs Menu
Docs Home
/
MongoDB Ops Manager
/

Getting Started

On this page

  • Authentication Errors
  • Check Agent Output or Log
  • Ensure Connectivity Between Agent and Monitored Hosts
  • Ensure Connectivity Between Agent and Ops Manager Server
  • Allow Agent to Discover Hosts and Collect Initial Data

To begin troubleshooting, complete these tasks to check for common, easily fixed problems:

If your MongoDB instances run with authentication enabled, ensure Ops Manager has the MongoDB credentials. To learn more, see Configure MongoDB Authentication and Authorization.

If you continue to encounter problems, check the agent's output for errors. To learn more, see Agent Logs for more information.

Ensure the system running the agent can resolve and connect to the mongod processes. If you install multiple Monitorings, ensure that each Monitoring can reach every mongod process in the deployment.

To confirm, log into the system where the agent is running and issue a command in the following form:

mongosh <hostname>:<port>

Replace <hostname> with the hostname and <port> with the port that the database is listening on.

Ops Manager does not support port forwarding.

Verify that the Monitoring can connect on TCP port 8443 (outbound) to the Ops Manager server (i.e. api-agents.mongodb.com.)

Allow the agent to run for 5 to 10 minutes to allow host discovery and initial data collection.

Back

Troubleshooting

Next

Authentication