search

commercetools / mongo-metrics-reporter

Sends mongodb db.serverStatus() to the graphite.
Apache License 2.0
3 stars 3 forks source link

Only getting subset of serverStatus data #14

Open waltari2001 opened 8 years ago

waltari2001 commented 8 years ago

I'm hitting a primary node in my replicaSet (v3.0) and only getting about 10-12 metrics.

OlegIlyenko commented 8 years ago

hmm.. it shroud be more. Are you using an InfluxDb or graphite reporter? Are you using an auto-discovery of mongod instances?

waltari2001 commented 8 years ago

I'm using the graphite reporter and have auto-discovery set to false. It seems like the metrics reporter stops after the "connections" block:

db.serverStatus() { "host" : "XXXXXXXXXXX", "version" : "3.0.1", "process" : "mongod", "pid" : NumberLong(52068), "uptime" : 18127, "uptimeMillis" : NumberLong(18126967), "uptimeEstimate" : 17897, "localTime" : ISODate("2016-06-21T19:50:08.859Z"), "asserts" : { "regular" : 0, "warning" : 0, "msg" : 0, "user" : 24, "rollovers" : 0 }, "connections" : { "current" : 114, "available" : 52314, "totalCreated" : NumberLong(1646) },

waltari2001 commented 8 years ago

Any update on this issue? Also is there a way to turn on debugging on the application to see what's reading/sending? Thanks!

OlegIlyenko commented 8 years ago

sorry for the late reply, completely missed it. There is not much logging going on in the reporter, the implementation is pretty rudimentary at the moment. Recently I mostly focused in an influxDB part because this is the one we are using at the moment. So it's possible that graphite reporter is not up-to-date. Now that I mentioned it, I just noticed that you are connecting it to mongo 3. graphite reporter is compatible with mogo 2.x, but was not yet updated to mongo 3.x (there is quite a few breaking changes in mongo). Influxdb reporter should work with mongo 3.x though.