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

Monitoring MongoDB With Monitis

Three common issues and how Monitis can help:

  • Too many connections: Open connections consume resources.  Too many open connections can take down your entire instance even if they are not running any queries.
  • More data than RAM: Keeping an eye on the “virtual memory” is the best way to gauge the performance of your Mongo instances.
  • Timeouts:  With a custom Monitis Monitor reading the HTTP Console you can find out if your database is throwing timeouts.

Monitis is for those running their own monitoring infrastructure. But if you want a hosted monitoring solution there are a couple of options available too: 10gen’s MongoDB Monitoring Service, Boxed Ice Server Density, and probably more that I’m forgetting right now.

Original title and link: Monitoring MongoDB With Monitis (NoSQL database©myNoSQL)

via: http://www.sys-con.com/node/2154083