Navigation
This version of the documentation is archived and no longer supported. It will be removed on 01 March 2021. 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.

Configure Ops Manager to Monitor Large Deployments

To monitor deployments with more than 2,000 hosts located in globally-distributed datacenters, configure your Ops Manager instance with these advanced settings.

Allocate more RAM to Ops Manager Hosts

  1. Open /opt/mongodb/mms/conf/mms.conf in your preferred text editor.
  2. Find a line where the JAVA_MMS_UI_OPTS variable defines the -Xms/-Xmx parameters.
  3. Update the values from the default of 4352 MB to 8192 MB or more if the hosts have extra free memory.

To learn about how to resolve this error in greater detail, see our troubleshooting entry on the OutOfMemoryError

Improve Monitoring Ingestion

Update app settings on all Ops Manager hosts to improve monitoring ingestion:

  1. Open /opt/mongodb/mms/conf/conf-mms.properties in your preferred text editor.

  2. Add the following properties:

    # Improved monitoring ingestion
    ingestion.thread.count=64
    ping.thread.count=32
    mms.monitoring.agentlog.writers=16
    mms.monitoring.ingestion.databasenames.poolsize=16
    mms.monitoring.ingestion.diskpartition.poolsize=16
    mms.monitoring.ingestion.groupupdate.poolsize=8
    mms.monitoring.ingestion.hostping.poolsize=32
    mms.monitoring.ingestion.hostversionchange.poolsize=8
    mms.monitoring.ingestion.ipaddresschange.poolsize=8
    mms.monitoring.ingestion.hostlogs.poolsize=16
    mms.monitoring.ingestion.munin.poolsize=16
    mms.monitoring.ingestion.newrelic.poolsize=16
    mms.monitoring.ingestion.profiler.poolsize=16
    mms.monitoring.ingestion.shardchunkcount.poolsize=16
    mms.monitoring.ingestion.totalstoragecache.poolsize=16
    mms.monitoring.rrd.rawdbperf.thread.count=16
    mms.monitoring.rrd.rawdbperf.batch.size=1000
    mms.monitoring.rrd.rawdbstorage.thread.count=16
    mms.monitoring.rrd.rawdbstorage.batch.size=1000
    mms.monitoring.rrd.rawdisk.thread.count=32
    mms.monitoring.rrd.rawdisk.batch.size=1000
    mms.monitoring.rrd.rawhost.thread.count=32
    mms.monitoring.rrd.rawhost.batch.size=1000
    mms.monitoring.rrd.rawmunin.thread.count=8
    mms.monitoring.rrd.rawmunin.batch.size=1000
    mms.monitoring.rrd.rawnamespace.thread.count=16
    mms.monitoring.rrd.rawnamespace.batch.size=1000
    mms.monitoring.rrd.rawprocess.thread.count=32
    mms.monitoring.rrd.rawprocess.batch.size=1000
    mms.monitoring.rrd.rawsystem.thread.count=32
    mms.monitoring.rrd.rawsystem.batch.size=1000
    
  3. Save the properties file.

  4. Restart Ops Manager.