Navigation
This version of the documentation is archived and no longer supported. To learn how to upgrade your version of MongoDB Ops Manager, refer to the upgrade documentation.
You were redirected from a different version of the documentation. Click here to go back.

Profile Databases

Overview

Monitoring can collect data from MongoDB’s profiler to provide statistics about performance and database operations.

Considerations

Before enabling profiling, be aware of these issues:

  • Profile data can include sensitive information, including the content of database queries. Ensure that exposing this data to Monitoring is consistent with your information security practices.
  • The profiler can consume resources which may adversely affect MongoDB performance. Consider the implications before enabling profiling.

Procedures

Enable Profiling

To allow Monitoring to collect profile data for a specific process:

Note

The Monitoring Agent attempts to minimize its effect on the monitored systems. If resource intensive operations, like polling profile data, begins to impact the performance of the database, Monitoring will throttle the frequency that it collects data. See How does Ops Manager gather database statistics? for more information about the agent’s throttling process.

When enabled, Monitoring samples profiling data from monitored processes. The agent sends only the most recent 20 entries from last minute.

With profiling enabled, configuration changes made in Ops Manager can take up to 2 minutes to propagate to the agent and another minute before profiling data appears in the Ops Manager interface.

1

Select the Deployment tab and then the Deployment page.

2

Click view mode, and then click the process’s gear icon and select Edit Host.

3

Click the Profiling tab.

4

Turn on profiling.

Click the button to toggle between Off and On. When the button is On, Ops Manager receives database profile statistics.

5

Start database profiling by using the mongo shell to modify the setProfilingLevel command.

See the database profiler documentation for instructions for using the profiler.

Display Profiling Levels

When profiling is on, the Profile Data tab displays profiled data. For more information on profiling, see the database profiler documentation in the MongoDB manual.

1

Select the Deployment tab and then the Deployment page.

2

Click view mode.

3

Select the Profile Data tab.

Delete Profile Data

Deleting profile data deletes the Web UI cache of the current profiling data. You must then disable profiling or drop or clear the source collection, or Ops Manager will repopulate the profiling data.

If Monitoring is storing a large amount of profile data for your instance, the removal process will not be instantaneous.

1

Select the Deployment tab and then the Deployment page.

2

Click view mode, and then click the process.

3

Select the Profile Data tab.

4

Click the Delete Profile Data button at the bottom of the page.

5

Confirm the deletion.

Ops Manager begins removing stored profile data from the server’s record. Ops Manager removes only the Web UI cache of the current profiling data. The cache quickly re-populates with the same data if you do not disable profiling or drop or clear the profiled collection.