ALL COVERED TOPICS

NoSQL Benchmarks NoSQL use cases NoSQL Videos NoSQL Hybrid Solutions NoSQL Presentations Big Data Hadoop MapReduce Pig Hive Flume Oozie Sqoop HDFS ZooKeeper Cascading Cascalog BigTable Cassandra HBase Hypertable Couchbase CouchDB MongoDB OrientDB RavenDB Jackrabbit Terrastore Amazon DynamoDB Redis Riak Project Voldemort Tokyo Cabinet Kyoto Cabinet memcached Amazon SimpleDB Datomic MemcacheDB M/DB GT.M Amazon Dynamo Dynomite Mnesia Yahoo! PNUTS/Sherpa Neo4j InfoGrid Sones GraphDB InfiniteGraph AllegroGraph MarkLogic Clustrix CouchDB Case Studies MongoDB Case Studies NoSQL at Adobe NoSQL at Facebook NoSQL at Twitter

NAVIGATE MAIN CATEGORIES

Close

MongoDB db.serverStatus() Explained: MongoDB Monitoring

The BoxedIce guys are continuing their series on Monitoring MongoDB, this time explaining parts of the db.serverStatus(): connections, index counters, background flushing (nb this is the part where MongoDB can lose your data), and opcounters.

MongoDB db.serverStatus() is similar in a way to MySQL SHOW VARIABLES LIKE 'Inno%' and SHOW ENGINE [INNODB] STATUS.

These aside, I assume this whole series is just a preamble for their upcoming MongoDB monitoring service.

Original title and link: MongoDB db.serverStatus() Explained: MongoDB Monitoring (NoSQL databases © myNoSQL)