Monitoring
On this page
Installation
The monitoring server does not start up successfully
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
Alerts
For resolutions to alert conditions, see also Resolve Alerts.
For information on creating and managing alerts, see Configure Alert Settings and Manage Alerts.
Cannot Turn Off Email Notifications
There are at least two ways to turn off alert notifications:
Remove the deployment from your Ops 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 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:
To access this feature, you must either:
Belong to the project
Have the Global Monitoring Admin role or the Global Owner role
Click the Deployment page.
Click the host's name.
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.
Deployments
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 Ops 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:
Click Deployment.
Click the Processes tab
Click Add Deployment.
In the New Deployment window, specify the following values:
deployment type
internal hostname
internal port
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.
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. Ops Manager detects the deployment as a duplicate and suppresses its data.
To reset:
Click Settings.
Click Project Settings.
Click Reset Duplicates.
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:
Warning
This deployment cannot be deleted because it is enabled for backup.
Contact MongoDB Support for help with deleting these deployments.
Projects
Additional Information on Projects
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.