Docs Menu
Docs Home
/
MongoDB Ops Manager
/

Monitoring

On this page

  • Installation
  • Alerts
  • Deployments
  • Projects

Confirm the URI or IP address for the Ops Manager service is stored correctly in the mongo.mongoUri property in the <install_dir>/conf/conf-mms.properties file:

mongo.mongoUri=<SetToValidUri>

If you don't set this property, Ops Manager will fail while trying to connect to the default 127.0.0.1:27017 URL.

If the URI or IP address of your service changes, you must update the property with the new address. For example, update the address if you deploy on a system without a static IP address, or if you deploy on EC2 without a fixed IP and then restart the EC2 instance.

If the URI or IP address changes, then each user who access the service must also update the address in the URL used to connect and in the client-side monitoring-agent.config files.

If you use the Ops Manager <install_dir>/bin/credentialstool to encrypt the password used in the mongo.mongoUri value, also add the mongo.encryptedCredentials key to the <install_dir>/conf/conf-mms.properties file and set the value for this property to true:

mongo.encryptedCredentials=true

For resolutions to alert conditions, see also Resolve Alerts.

For information on creating and managing alerts, see Configure Alert Settings and Manage Alerts.

There are at least two ways to turn off alert notifications:

If the notification email list contains multiple email-groups, one or more people may receive multiple notifications of the same alert.

These error messages appear on the Deployment page, under a host's name. They appear if the number of available connections does not meet the Ops Manager-defined minimum value. These errors are not generated by the mongos instance and, therefore, not appear in mongos log files.

On a host by host basis, the Monitoring compares the number of open file descriptors and connections to the maximum connections limit. The max open file descriptors ulimit parameter directly affects the number of available server connections. The agent calculates whether or not enough connections exist to meet the Ops Manager-defined minimum value.

In ping documents, for each node and its serverStatus.connections values, if the sum of the current value plus the available value is less than the maxConns configuration value set for a monitored host, the Monitoring will send a Host has low open file limits or Too many open files message to Ops Manager.

Ping documents are data sent by Monitorings to Ops Manager. To view ping documents:

Note

To access this feature, you must either:

  1. Click the Deployment page.

  2. Click the host's name.

  3. Click Last Ping.

To prevent this error, we recommend you set ulimit open files to 64000. We also recommend setting the maxConns command in mongosh to at least the recommended settings.

To learn more, see the MongoDB ulimit reference page and the the MongoDB maxConns reference page.

Possible causes for this state:

  • The Monitoring can't connect to the server because of networking restrictions or issues (i.e. firewalls, proxies, routing.)

  • Your database is running with TLS. You must enable TLS either globally or on a per-host basis. To learn more, see Configure MongoDB Agent to Use TLS and Enable TLS for a Deployment.

  • Your database is running with authentication. You must supply Ops Manager with the authentication credentials for the host. See Configure MongoDB Authentication and Authorization.

The following factors can cause problems with the Monitoring detecting deployments:

To fix this issue:

  1. Click Deployment.

  2. Click the Processes tab

  3. Click Add Deployment.

  4. In the New Deployment window, specify the following values:

    • deployment type

    • internal hostname

    • internal port

  5. If appropriate:

    • Add the database username and password.

    • Enable TLS to connect with your Monitoring.

Note

You don't need to restart your Monitoring when you add (or remove) a deployment.

If you add the deployment after a crash and restart the Monitoring, you might not see the hostname on the Deployment page. Ops Manager detects the deployment as a duplicate and suppresses its data.

To reset:

  1. Click Settings.

  2. Click Project Settings.

  3. Click Reset Duplicates.

If your deployments exist across multiple data centers, ensure that all of your deployments can be discovered by all of your Monitorings.

In rare cases, the mongod is brought down and the replica set is reconfigured. The down deployment can't be deleted and returns the following error message:

Warning

This deployment cannot be deleted because it is enabled for backup.

Contact MongoDB Support for help with deleting these deployments.

Create a project to monitor additional segregated systems or environments for servers, agents, users, and other resources.

Example

Firewalls may separate your deployment among two or more environments. In this case, you would need two or more separate Ops Manager projects.

API keys are unique to each project. Each project requires its own agent with the appropriate API keys. Within each project, the agent needs to be able to connect to all hosts it monitors in the project.

To learn more about creating and managing projects, see Projects.

Back

Automation

Next

Upgrade Issues