As common use, just show the ip of mongos(query_router) and data nodes(member) of cluster is fine.
And if you want more detail, use mgmt, it will show all nodes include config_node, data_node, and mongos.
The architecture of these database is different(cassandra, galera, redis, vertica, mongo...), which means instance nodes to be publish could be different.
So, I think it's not a bug.
******* ******* ******* ******* ******* ******* ******* ******* ******* **** iew(ClusterView ):
class MongoDbClusterV
def build_instances (self): instances( ['query_ router' ], ['member'])
return self._build_
class MongoDbMgmtClus terView( MgmtClusterView ):
def build_instances (self): instances( ['query_ router' ],
['config_ server' ,
'member' ,
'query_ router' ]) ******* ******* ******* ******* ******* ******* ******* ******* **
return self._build_
*******
As common use, just show the ip of mongos( query_router) and data nodes(member) of cluster is fine.
And if you want more detail, use mgmt, it will show all nodes include config_node, data_node, and mongos.
The architecture of these database is different( cassandra, galera, redis, vertica, mongo...), which means instance nodes to be publish could be different.
So, I think it's not a bug.