Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Database-level stats #6

Open
pataquets opened this issue Nov 7, 2016 · 0 comments
Open

Database-level stats #6

pataquets opened this issue Nov 7, 2016 · 0 comments

Comments

@pataquets
Copy link
Contributor

It would be nice to iterate on all or some configurable list of databases and send their stats.
Example:

> db.stats()
{
	"db" : "main",
	"collections" : 12,
	"objects" : 10169918,
	"avgObjSize" : 3109.8305005015773,
	"dataSize" : 31626721184,
	"storageSize" : 41310953280,
	"numExtents" : 113,
	"indexes" : 22,
	"indexSize" : 2132815888,
	"fileSize" : 47155511296,
	"nsSizeMB" : 16,
	"dataFileVersion" : {
		"major" : 4,
		"minor" : 5
	},
	"extentFreeList" : {
		"num" : 0,
		"totalSize" : 0
	},
	"ok" : 1
}

What would be the correct statsd metric naming? Which metrics to include/skip?
Would it be an initial requirement from the beginning to make it optional? And to use/have a list of included and/or excluded dbs? Initially, just iterating on all dbs would do fine.
Later, table-level metrics could possibly follow suit.

Although I'm no Go programmer, code is nicely laid out and it will make for a perfect beginner contributor task. This is why I'm asking so many questions.

Should I find time to dive into Go programming :) , I will take a stab at doing ti, but no commitment, atm.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants