Tokutek / mongo

TokuMX is a high-performance, concurrent, compressing, drop-in replacement engine for MongoDB | Issue tracker: https://tokutek.atlassian.net/browse/MX/ |
http://www.tokutek.com/products/tokumx-for-mongodb/
703 stars 97 forks source link

Missing values for backgroundFlushing/mem in db.serverStatus() #460

Open byzhang opened 11 years ago

byzhang commented 11 years ago

I know they maybe are not available for TokuMX, but could we add some dummy values to be compatible with some mongodb monitoring tools?

esmet commented 11 years ago

I would imagine most mongodb monitoring tools would have some default value for missing fields (say, 0 for an integer field).

Do you know of any tools that break / behave badly when fields are absent from db.serverStatus()?

byzhang commented 11 years ago

Both motop and mtop (listed in http://docs.mongodb.org/manual/administration/monitoring/) are broken. It's hard to say it's TokuMX's fault. Those monitoring tools simply assume the backgroundFlushing/mem keys exist in the output of serverStatus. I'm not sure how about other monitoring tools though.

Thanks, -B

On Mon, Aug 19, 2013 at 12:41 PM, John Esmet notifications@github.comwrote:

I would imagine most mongodb monitoring tools would have some default value for missing fields (say, 0 for an integer field).

Do you know of any tools that break / behave badly without these fields present in db.serverStatus()

— Reply to this email directly or view it on GitHubhttps://github.com/Tokutek/mongo/issues/460#issuecomment-22898642 .

leifwalsh commented 11 years ago

see also #510

leifwalsh commented 11 years ago

see also #591