Couchbase recommending, it is best to run all your stat commands against port 11210 which will always give you the information for the specific node that you are sending the request to. It is a best practice to then aggregate the relevant data across nodes at a higher level (in your own script or monitoring system).
When you run the stats commands without supplying a bucket name and/or password, they will return results for the default bucket and produce an error if one does not exist.
To access a bucket other than the default, you will need to supply the bucket name and password on the end of the command. Any bucket created on a dedicated port does not require a password.
You get this only at node level and not cluster.
Do this for each node, after ssh into the node(example):
Syntax: Max connections followed by current connections
/opt/couchbase/bin/cbstats -b Bucket_Name IP:11210 all -u Administrator -p pa$$word | grep max_conns_on_port
/opt/couchbase/bin/cbstats -b Bucket_Name IP:11210 all -u Administrator -p pa$$word | grep curr_conns_on_port
/opt/couchbase/bin/cbstats -b beer-sample 18.104.22.168:11210 all -u Administrator -p pa$$word | grep max_conns_on_port
/opt/couchbase/bin/cbstats -b beer-sample 22.214.171.124:11210 all -u Administrator -p marriottram123 | grep curr_conns_on_port
For more information, refer cbstats documentation to retrieve lower level statistics with the
cbstats utility, which provides deep insight into what occurs within a cluster.