Database Commands Used by Monitoring
- OAuth 2.0 authentication for programmatic access to Cloud Manager is available as a Preview feature.
- The feature and the corresponding documentation might change at any time during the Preview period. To use OAuth 2.0 authentication, create a service account to use in your requests to the Cloud Manager Public API.
The Monitoring uses a set of MongoDB diagnostic, administrative, and other database commands to report on the status of your MongoDB deployment. The agent uses these commands:
_isSelf
collStats
on the following local database collections, which support replication operations:local.oplog.rs
dbStats
The Monitoring collects storage statistics for a given database at 20 minute intervals.find
on the following config database collections, which support sharding operations:config.chunks
config.collections
config.databases
config.lockpings
config.mongos
config.settings
config.shards
find
on the following local database collections, which support replication operations:local.system.replset
find
on thesystem.profile <<database>.system.profile>
collection. Only if database profiling is enabled. Database profiling is disabled by default.findOne
on thelocal.oplog.rs
collection. Only for MongoDB v2.6 and earlier.getLog
issued with:A value of
global
. Only if you have enabled log collection.A value of
startupWarnings
.
getParameter
issued with a value of*
profile
. Only if database profiling is enabled. Database profiling is disabled by default.