-
Type: Bug
-
Resolution: Done
-
Priority: Minor - P4
-
Affects Version/s: 2.5.3
-
Component/s: Diagnostics
-
Environment:* MongoDB 2.5.4-pre Ubuntu 12.04 Enterprise
* Amazon EC2 m1.medium Ubuntu Server LTS 12.04
* Master/Slave
-
ALL
-
Example snmpwalk output:
MONGO-MIB::replSetName."27017" = "" MONGO-MIB::replSetName."27018" = "" MONGO-MIB::replSetVersion."27017" = INTEGER: 0 MONGO-MIB::replSetVersion."27018" = INTEGER: 0 MONGO-MIB::replIsMaster."27017" = INTEGER: 0 MONGO-MIB::replIsMaster."27018" = INTEGER: 0 MONGO-MIB::replIsSecondary."27017" = INTEGER: 0 MONGO-MIB::replIsSecondary."27018" = INTEGER: 0 MONGO-MIB::replPrimary."27017" = "" MONGO-MIB::replPrimary."27018" = "" MONGO-MIB::replMe."27017" = "" MONGO-MIB::replMe."27018" = "" MONGO-MIB::replMe."27018" = No more variables left in this MIB View (It is past the end of the MIB tree)
By comparison, db.serverStatus() is reporting a subdocument such as:
"repl" : { "ismaster" : [true|false] },
I would expect the isMaster/isSecondary SNMP booleans to also represent master/slave status accordingly.