Docs Menu

Docs HomeMongoDB Manual


On this page

  • Definition
  • Syntax
  • Behavior
  • Access Control


Free monitoring is deprecated

Free monitoring was deprecated in April 2023 and will be decommissioned in August 2023.

Beginning in April 2023, you can’t enable free monitoring on MongoDB Community instances. Deployments currently using free monitoring can continue to access the free monitoring UI until August 2023.

You can choose another monitoring option for your deployment:


New in version 4.0: Available for MongoDB Community Edition.

Enables or disables free Cloud monitoring for standalones and replica sets.

The command is run against the admin database.


To run setFreeMonitoring, you must have specified --enableFreeMonitoring command-line option or configuration file set to runtime.

Otherwise, you can only enable or disable at startup. See --enableFreeMonitoring command-line option or for details.

The command has the following syntax:

setFreeMonitoring: 1,
action: "<enable|disable>"

Once enabled, the free monitoring state remains enabled until explicitly disabled. That is, you do not need to re-enable each time you start the server.

mongosh provides the following helper methods for setFreeMonitoring:

You can use db.getFreeMonitoringStatus() to check your free monitoring status.

When running with access control, the user must have the setFreeMonitoring privilege actions on the cluster. That is, a user must have a role that grants the following privilege:

{ resource: { cluster : true }, actions: [ "setFreeMonitoring" ] }

The built-in role clusterMonitor role provides this privilege.

←  getFreeMonitoringStatusSystem Events Auditing Commands →
Share Feedback
© 2023 MongoDB, Inc.


  • Careers
  • Investor Relations
  • Legal Notices
  • Privacy Notices
  • Security Information
  • Trust Center
© 2023 MongoDB, Inc.