• Reference >
• Database Commands Used by Monitoring

Database Commands Used by Monitoring

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
• buildInfo
• collStats on the following local database collections, which support replication operations:
  • local.oplog.rs
  • local.oplog.$main. Only for master-slave replication
• connPoolStats
• dbStats
• 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
  • local.sources. Only for master-slave replication
• find on the system.profile collection. Only if database profiling is enabled. Database profiling is disabled by default.
• findOne on the local.oplog.rs collection. Only for MongoDB v2.6 and earlier.
• getCmdLineOpts
• getLog issued with:
  • A value of global. Only if you have enabled log collection.
  • A value of startupWarnings.
• getParameter issued with a value of *
• getShardVersion
• hostInfo
• isMaster
• listDatabases
• netstat
• ping
• profile. Only if database profiling is enabled. Database profiling is disabled by default.
• replSetGetStatus
• serverStatus

←   AWS IAM Policy Alert Event Types  →

© MongoDB, Inc 2008-present. MongoDB, Mongo, and the leaf logo are registered trademarks of MongoDB, Inc.