Monitoring

Cannot Turn Off Email Notifications

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

• Remove the deployment from your Cloud Manager account. See Stop Managing and/or Monitoring One Deployment.

• Disable or delete the alert configuration. See Configure Alert Settings.

• Turn off alerts for a specific host. See Disable Alerts for a Specific Process.

Receive Duplicate Alerts

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

Receive "Host has low open file limits" or "Too many open files" error messages

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 Cloud 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 Cloud 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 Cloud Manager.

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

To access this feature, you must have the Project Owner or Project Data Access Admin Cloud Manager user role.

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.

Monitoring Fails to Collect Data

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 Cloud Manager with the authentication credentials for the host. See Configure MongoDB Authentication and Authorization.

Deployments Aren't Visible

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

Deployment Not Added

To fix this issue:

Accidental Duplicate mongod

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

To reset:

Monitorings Can't Detect Deployments

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

Can't Delete a Deployment

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:

Contact MongoDB Support for help with deleting these deployments.

Additional Information on Projects

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

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.