Advanced Options for MongoDB Deployments
On this page
The following mongod and mongos configuration options are available through the Ops Manager Advanced Configuration Options field when you deploy MongoDB. You select advanced options when deploying:
The Ops Manager Advanced Configuration Options map to the MongoDB configuration options and parameters described as follows.
Warning
Limited to Listed Options
If a MongoDB option isn't listed on this page, you may use setParameter to add the setting. Settings added in this way apply to MongoDB instances that Ops Manager manages when those instances start up.
Procedure
To edit Advanced Options, complete the following steps.
Navigate to the Deployment page for your project.
If it is not already displayed, select the organization that contains your desired project from the Organizations menu in the navigation bar.
If it is not already displayed, select your desired project from the Projects menu in the navigation bar.
If it is not already displayed, click Deployment in the sidebar.
Navigate to the Processes tab for your deployment.
If it is not already displayed, select the organization that contains your desired project from the Organizations menu in the navigation bar.
If it is not already displayed, select your desired project from the Projects menu in the navigation bar.
Click Processes in the sidebar.
Audit Log
Ops Manager Interface | MongoDB Option |
---|---|
auditEncryptionKeyIdentifier | |
compressionMode | |
auditDestination | |
auditFilter | |
auditFormat | |
localAuditKeyFile | |
auditPath | |
schema | auditLog.schema |
You can add these audit log parameters with a setParameter
option in the Advanced Configuration Options section.
To encrypt the audit log, before you start MongoDB instances that
Ops Manager manages, add the auditEncryptKeyWithKMIPGet
and auditEncryptionHeaderMetadataFile
parameters in the
Advanced Configuration Options section.
Basis Tech
Ops Manager Interface | MongoDB Option |
---|---|
basisTechRootDirectory | basisTech.rootDirectory |
Kerberos
Ops Manager Interface | MongoDB Option |
---|---|
kerberosKeytab | kerberos.keytab |
Net
Ops Manager Interface | MongoDB Option |
---|---|
bind_ip | |
httpinterface | net.http.enabled |
ipv6 | |
jsonp | net.http.JSONPEnabled |
maxConns | |
rest | net.http.RESTInterfaceEnabled |
tlsClusterFile | |
tlsClusterPassword | |
tlsCRLFile | |
tlsDisabledProtocols | |
tlsLogVersions |
Numactl
Ops Manager Interface | MongoDB Option |
---|---|
numCores | numactl.numCores |
Operation Profiling
Ops Manager Interface | MongoDB Option |
---|---|
profile | |
slowms | |
slowOpSampleRate |
Process Management
Ops Manager Interface | MongoDB Option |
---|---|
pidfilepath |
Replication
Ops Manager Interface | MongoDB Option |
---|---|
enableMajorityReadConcern | |
oplogSize |
Security
Warning
Ops Manager doesn't support transitioning from local key encryption to KMIP server-based encryption.
Ops Manager Interface | MongoDB Option |
---|---|
clusterAuthMode | |
enableEncryption | |
encryptionCipherMode | |
encryptionKeyFile | |
javascriptEnabled This setting is deprecated and will be removed
in a future release. Defaults to | |
kmipClientCertificateFile | |
kmipClientCertificatePassword | |
kmipKeyIdentifier | |
kmipPort | |
kmipServerCAFile | |
kmipServerName | |
saslauthdSocketPath | |
saslHostname |
Sharding
Ops Manager Interface | MongoDB Option |
---|---|
autoSplit | sharding.autoSplit |
chunkSize | sharding.chunkSize |
Storage
Ops Manager Interface | MongoDB Option |
---|---|
directoryperdb | |
engine | |
inMemorySizeGB | |
journal | storage.journal.enabled |
journalCommitInterval | |
nssize | storage.nsSize |
prealloc | storage.preallocDataFiles |
quota | storage.quota.enforced |
quotaFiles | storage.quota.maxFilesPerDB |
repairpath | storage.repairPath |
smallfiles | storage.smallFiles |
syncdelay | |
wiredTigerCacheSizeGB | |
wiredTigerCollectionBlockCompressor | |
wiredTigerCollectionConfigString | storage.wiredTiger.collectionConfig.configString |
wiredTigerDirectoryForIndexes | |
wiredTigerEngineConfigString | storage.wiredTiger.engineConfig.configString |
wiredTigerIndexConfigString | storage.wiredTiger.indexConfig.configString |
wiredTigerIndexPrefixCompression | |
wiredTigerJournalCompressor | |
wiredTigerStatisticsLogDelaySecs | storage.wiredTiger.engineConfig.statisticsLogDelaySecs |
System Log
Ops Manager Interface | MongoDB Option |
---|---|
logappend | |
logRotate | |
quiet | |
syslogDestination | |
syslogFacility | |
timeStampFormat | |
verbosity |
TLS
Ops Manager Interface | MongoDB Option |
---|---|
tlsCertificateKeyFile | |
tlsCertificateKeyFilePassword | |
tlsFIPSMode | |
tlsMode |
Set Parameter
Important
Ops Manager does not check to see if the parameters you provide are valid. Check the MongoDB Server Manual for accepted parameters and values.
Ops Manager Interface | MongoDB Option |
---|---|
[setParameter] |
You can add any value from
Server Parameters as a
|
For supported MongoDB versions and MongoDB Agent versions, you can set
certain setParameter
parameters without a rolling restart.
To determine whether you can set a setParameter
parameter during
runtime or upon startup, retrieve details
on that parameter. For complex setParameter
parameters, you must set
the parameter values in the same format as in the process configuration
file or in the --setParameter
command line option.
Note
If you set the watchdogPeriodSeconds parameter, MongoDB Agent triggers a rolling restart.
If you delete or remove a parameter, MongoDB Agent keeps the parameter's current value until you make another change to that parameter. To reset the parameter to its default value, you must manually set the value or trigger a rolling restart.
If you attempt to set a parameter that MongoDB Agent can't set at startup,
MongoDB Agent triggers a rolling restart and fails to start up a
mongod
instance.