December 4, 2011 2

Monitoring mongoDB with MMS (from 10gen)

By in Monitoring

Mongodb et monitoringMongoDB is an excellent way to begin with the  nosql concept.

It has an extensive documentation, supported by both it’s active creators AND community, has been ported to all professionnal environments, enough drivers so that you CANNOT NOT try it, great / hype / trending companies using it in production, all this and even more is way enough to make you give it a try. But that’s not my point here.

The company I’m working for decided to throw all it’s efforts into one hell of a project a couple of months ago, and of course, you would guess, we adopted mongo.

What we didn’t know by the time we started working was what was going to happen to that project : frozen. Yes, it’s now frozen until further and undisclosed criterias. The project’s clearly not dead. No, it’s just that our small start up has enough work for tens of techies, and… we’re three. That’s why we decided not just to forget this project for this lapse of time (estimated to three months), but to retrieve as much data as possible during this pause. Not just to have data, *duh*, but to be able to understand what we did really wrong, what could be better, and what we got right.

That’s how I discovered the MongoDb Monitoring Service (MMS).

Free agent for all your mongo replica sets, shards etc …

Thats right, free.  MMS is a tool generously offered by 10gen to all users of there awesome database. This agent (python, f.y.i) is quite easy to install. After setting up an account, simply download the agent (wich is configured with your credentials) on next to your mong server. This is all. The agent will automatically be aware of all your shards, and retrieve data from them to be monitored.

So, what data is monitored ?

  • cpu time
  • db storage
  • page faults
  • repl lag
  • replica
  • network
  • cursors
  • queues
  • connections
  • background flush avg
  • lock %
  • btree
  • non-mapped virtual memory
  • memory
  • asserts
  • opcounters-repl
  • opcounters
  • collections
  • objects
  • average object size
  • data size
  • storage size
  • num extents
  • indexes
  • index size
  • file size

My only regrets would concern the absence of customized alerts, via mail, sms, jabber etc …, based on the data and thresholds you could set. At the moment, the only way to check how everything’s going is to login to the web interface of MMS. Feels not enough for a monitoring service.

That said, you can’t deny this service is a excellent start, and a great move from 10gen. About these custom alerts, I sent a quick mail to get info about that, and, less than 15 minutes later, I got an answer from Max Schireson:

 Yes, we are planning to add user customizable alerting. We think it will be very popular, but I can’t give a specific release date right now.

That kind of higly reactive free support is pretty cool. 10gen shows that, while their products are still quite early adopted, they want to move well, and fast.

So, if you didn’t here about MMS, what are you waiting for, christmas ?

Oh, and here’s one last quick tip : Manning publications just released Mongodb in action, so if you want to grab your paperback and/or digital copy of the book, it’s now the right time, as you can get a 39% discount by using the code

mongo39svem

That’s right baby !

2 Responses to “Monitoring mongoDB with MMS (from 10gen)”

  1. Ryan says:

    Generic/field/metric alerts will be released very soon (possibly this week). If you would like access to the beta program, create a private jira ticket here (same credentials used for MMS):

    https://jira.mongodb.org/secure/CreateIssue.jspa?pid=10582&issuetype=6&Create=Create

  2. Tom says:

    Sympa de présenter ce super produit (qui sert surtout de prospection à cette jeune start-up qui enchaine les levées de fond ;-)

    Et donc un avis sur Mongo et l’utilité de cet outil ?

Leave a Reply